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

refac: Remove unnecessary triggers and steps in GitHub Actions #520

Merged
merged 2 commits into from
Nov 1, 2023

Conversation

wkyoshida
Copy link
Member

Contributor checklist


Description

Working on #429 , I noticed a couple points in our existing workflows:

  • Was wondering if the Checkout step was necessary in the pr_maintainer_checklist.yaml, since the workflow doesn't perform any steps actually involving the source code. Tried removing this step and tested in my fork:

  • Also, the workflow_run triggers in the pr_ci_backend.yaml and the pr_ci_frontend.yaml appear to be redundant, since there is already a trigger for when the pull_request is opened. The pr_maintainer_checklist workflow is completed mere seconds after the pull_request is opened, so this simply causes an unnecessary duplicate CI run.

    • Notice the duplicate pr_ci_backend and pr_ci_frontend runs for the PR yesterday created for 🌿
      image
    • Notice in the test PR from above, no duplicate CI runs occur 😁
      image

Related issue

Copy link
Contributor

github-actions bot commented Nov 1, 2023

Thank you for the pull request!

The activist team will do our best to address your contribution as soon as we can. The following is a checklist for maintainers to make sure this process goes as well as possible. Feel free to address the points below yourself in further commits if you realize that actions are needed :)

If you're not already a member of our public Matrix community, please consider joining! We'd suggest using Element as your Matrix client, and definitely join the General and Development rooms once you're in. It'd be great to have you!

Maintainer checklist

  • The commit messages for the remote branch should be checked to make sure the contributor's email is set up correctly so that they receive credit for their contribution

    • The contributor's name and icon in remote commits should be the same as what appears in the PR
    • If there's a mismatch, the contributor needs to make sure that the email they use for GitHub matches what they have for git config user.email in their local activist repo
  • The TypeScript and formatting workflows within the PR checks do not indicate new errors in the files changed

  • The CHANGELOG has been updated with a description of the changes for the upcoming release and the corresponding issue (if necessary)

Copy link

netlify bot commented Nov 1, 2023

Deploy Preview for activist-org canceled.

Name Link
🔨 Latest commit 52ae4d7
🔍 Latest deploy log https://app.netlify.com/sites/activist-org/deploys/6541a851d974c30009bebd3c

@wkyoshida
Copy link
Member Author

Likely not dire in our current situation, but thought of this refac to avoid unnecessary GitHub Actions usage, as there is in fact a limit on used minutes.

@andrewtavis
Copy link
Member

Thanks for the consideration on this, @wkyoshida! :) Great to cut it down as we can 😊

@andrewtavis andrewtavis added the hacktoberfest-accepted Accepted as a part of Hacktoberfest label Nov 1, 2023
Copy link
Member

@andrewtavis andrewtavis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Makes sense and looks good to me, @wkyoshida! If there's something like this on the Scribe end, could you also open PRs? Thanks! 🙏

@andrewtavis andrewtavis merged commit c25abc5 into activist-org:main Nov 1, 2023
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
hacktoberfest-accepted Accepted as a part of Hacktoberfest
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants