58b7906fe6
* GitHub workflow for /ci trigger Add in GitHub workflow for adding the `ci` label to the PR and running Buildkite pipeline(s). The `ci` label will allow the PR to be built on push without havinvg to continuously issue the `/ci` trigger from a Forem team member. ``` build.pull_request.repository.fork != true || build.pull_request.labels includes "ci" ``` Also using the `/ci` trigger will run the initial pipeline builds too. * Fix YAML formatting and typos. * Add note to PR template. * Conditionally add a comment to a new PR when it originates from a third-party fork with a note about having to wait for manual approval for our CI to run on their PR. * Update .github/PULL_REQUEST_TEMPLATE.md Co-authored-by: Michael Kohl <citizen428@dev.to> * Update .github/workflows/pr.yml Co-authored-by: Michael Kohl <citizen428@dev.to> * Adjust if statement to include OWNERS and do startsWith instead of contains. Co-authored-by: Michael Kohl <citizen428@dev.to>
2.2 KiB
2.2 KiB
What type of PR is this? (check all applicable)
- Refactor
- Feature
- Bug Fix
- Optimization
- Documentation Update
Description
Related Tickets & Documents
QA Instructions, Screenshots, Recordings
Please replace this line with instructions on how to test your changes, as well as any relevant images for UI changes.
UI accessibility concerns?
If your PR includes UI changes, please replace this line with details on how accessibility is impacted and tested. For more info, check out the Forem Accessibility Docs.
Added tests?
- Yes
- No, and this is why: please replace this line with details on why tests have not been included
- I need help with writing tests
Added to documentation?
- Developer Docs and/or Admin Guide
- README
- No documentation needed
