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

Actions: New PR labeling and issue link workflows #1149

Merged
merged 3 commits into from
Oct 4, 2024

Conversation

kyleecodes
Copy link
Member

@kyleecodes kyleecodes commented Sep 24, 2024

Resolves #enter-issue-number

N/A

What changes did you make and why did you make them?

New workflows added to create more data points for gaining insight on PR activity:

  1. Automated pr labels from issue labels
  2. Check for linked issue in pr
  3. Automated pr labels indicating review status (to help visually see which prs need attention)

TODO:

  • DRY with utils
  • exclude prs opened by staff from automated labeling requirement
  • tag issue author / tech community manager for review

Did you run tests? Share screenshot of results:

N/A

How did you find us? (GitHub, Google search, social media, etc.):

N/A

Copy link
Contributor

@kyleecodes, this Pull Request is not linked to a valid issue. Above, on the first line of your PR, please link the number of the issue that you worked on using the format of 'Resolves #' + issue number, for example: Fixes #9876

Note: Do not use the number of this PR or URL for issue. Chayn staff may disregard this. A linked issue is required for automated PR labeling.

Copy link

vercel bot commented Sep 24, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
bloom-frontend ✅ Ready (Inspect) Visit Preview 💬 Add feedback Oct 4, 2024 4:41pm

Copy link
Contributor

github-actions bot commented Oct 4, 2024

@kyleecodes, this Pull Request is not linked to a valid issue. Above, on the first line of your PR, please link the number of the issue that you worked on using the format of 'Resolves #' + issue number, for example: Fixes #9876

Note: Do not use the number of this PR or URL for issue. Chayn staff may disregard this. A linked issue is required for automated PR labeling.

@kyleecodes kyleecodes merged commit 22e3fae into develop Oct 4, 2024
7 checks passed
Copy link

cypress bot commented Oct 4, 2024

Bloom frontend    Run #746

Run Properties:  status check passed Passed #746  •  git commit 22e3fae27e: Actions: New PR labeling and issue link workflows (#1149)
Project Bloom frontend
Branch Review develop
Run status status check passed Passed #746
Run duration 08m 57s
Commit git commit 22e3fae27e: Actions: New PR labeling and issue link workflows (#1149)
Committer Kylee Fields
View all properties for this run ↗︎

Test results
Tests that failed  Failures 0
Tests that were flaky  Flaky 0
Tests that did not run due to a developer annotating a test with .skip  Pending 5
Tests that did not run due to a failure in a mocha hook  Skipped 0
Tests that passed  Passing 86
⚠️ You've recorded test results over your free plan limit.
Upgrade your plan to view test results.
View all changes introduced in this branch ↗︎

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant