This should be the last PR to get the `/ci` and `/rebase` commands working in
GitHub Actions. The issue is that our membership settings for `forem/forem` have
everyone set to 'CONTRIBUTOR' instead of 'MEMBER' or 'OWNER'.
Adding github.event.comment.author_association == 'CONTRIBUTOR' should fix this
issue.
I also cleaned up all action files to make the main name of the workflow as
succinct as possible to better organize the left menut of the GitHub Actions
page.
This PR won't fix the issues with the "Run forem/build-containers pipeline"
job in buildkite.yml but I will address those issues in another PR.
* Update if statement w/r/t github.event.issue.pull_request conditional and update
cirrus-actions/rebase to 1.4.
* Fix running the PR comment workflow so it only runs if
github.event.pull_request.head.repo.full_name != github.repository
How neat!
* 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>
* Update to Ruby 2.7.2
* Update remaining files
* Remove VERBOSE from development.rb and test.rb
* Update Ruby version for dependabot and docs
* Readd accidentally removed code
GitHub released a code analysis engine that scans the code for potential issues called CodeQL.
Among the list of supported languages we only use JavaScript
* Allow org owners to kick off automatic rebase
I suspect without this change PBJ couldn't kick off the automatic rebase
workflow.
This also includes a tweak to our method for determining if this is a
comment on a PR. I personally think this method is more explicit and
therefore readable.
* Add explanatory comment to rebase workflow
This might help someone determine what the workflow does at a glance, it
also documents a slightly unexpected caveat: The workflow can't be
triggered if your organization membership is private.
* Trigger Travis
Co-authored-by: rhymes <rhymesete@gmail.com>
* Enable Automatic Rebase: Fix#8927
* Update rebase.yml to use startsWith
Use startsWith() instead of contains() in Github Action so as to prevent accidental Rebase of PRs.