Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Documentation:Developer] Add testing guide for external devs #670

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
25 changes: 25 additions & 0 deletions _docs/developer/testing/external_contributors.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,25 @@
---
title: External Contributors
---

To run all Submitty workflows on a forked repository, you must manually trigger the workflow. This is because GitHub Actions do not run on forked repositories by default. One of the people in the Submitty organization must manually trigger the workflow for you. To avoid this, you can trust the workflow in your forked repository. This will allow GitHub Actions to run on your forked repository without manual intervention.

---

## Steps for External Contributors

1. The first step is to visit [https://github.com/GITHUB_USERNAME/Submitty/actions](https://github.com/GITHUB_USERNAME/Submitty/actions) (or click the actions tab from your forked submitty repository) and click on the button labeled "I understand my workflows, go ahead and enable them".
![GitHub UI to trust workflows in fork](/images/fork_trust.png)

2. After that, on the left side of the page, click on the workflow labeled "CI" to be able to run the workflow. Then, in the "Run workflow" dropdown, select the branch you want to run the workflow on and click the green "Run workflow" button.
![GitHub UI to manually trigger workflow](/images/fork_dispatch.png)
3. Congratulations! You have successfully triggered the workflow on your forked repository. You should now see a new started workflow in the list of workflows.
![GitHub UI to view workflow run](/images/fork_workflow_run.png)

---

These steps are drawn from:

[https://github.com/github/docs/issues/15761](https://github.com/github/docs/issues/15761)

[https://docs.github.com/en/actions/managing-workflow-runs-and-deployments/managing-workflow-runs/manually-running-a-workflow](https://docs.github.com/en/actions/managing-workflow-runs-and-deployments/managing-workflow-runs/manually-running-a-workflow)
Binary file added images/fork_dispatch.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added images/fork_trust.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added images/fork_workflow_run.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
1 change: 1 addition & 0 deletions navtreedata.js
Original file line number Diff line number Diff line change
Expand Up @@ -214,6 +214,7 @@ var NAVTREE =
[ "Localization / Language Support", "/developer/development_instructions/localization", null ],
[ "Continuous Integration Testing", "/developer/testing/index", [
[ "Overview", "/developer/testing/index", null ],
["External Contributors", "/developer/testing/external_contributors", null],
[ "Installing PHP", "/developer/testing/install_php", null ],
[ "Linting / Static Analysis", "/developer/testing/linting_static_analysis", null ],
[ "Python Unit Tests", "/developer/testing/python_unit_tests", null ],
Expand Down
Loading