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

Don't run review jobs on tagged releases on next #670

Merged
merged 1 commit into from
Sep 10, 2024

Conversation

ivomurrell
Copy link
Contributor

Description

Port of #669 to next. From the original PR's description:

We are already running staging jobs on tagged releases, so we don't need to run review jobs too. In addition, the HerokuReview task will fail as it can't find a branch to associate the review app with. For an example of why this is a problem, see next-router's CI workflow with its unnecessary tool-kit/deploy-review-node branch.

Checklist:

  • My branch has been rebased onto the latest commit on main (don't merge main into your branch)
  • My commit messages are conventional commits, for example: feat(circleci): add support for nightly workflows, fix: set Heroku app name for staging apps too

@ivomurrell ivomurrell requested a review from a team as a code owner July 22, 2024 10:19
@ivomurrell ivomurrell force-pushed the next-circleci-skip-review-jobs branch from 26466f8 to 3e2970e Compare July 22, 2024 14:45
Base automatically changed from next to main September 5, 2024 15:54
Port of 35a24dc, original description
follows:

We are already running staging jobs on tagged releases, so we don't need
to run review jobs too. In addition, the HerokuReview task will fail as
it can't find a branch to associate the review app with.
@ivomurrell ivomurrell merged commit da05eaf into main Sep 10, 2024
14 checks passed
@ivomurrell ivomurrell deleted the next-circleci-skip-review-jobs branch September 10, 2024 13:15
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.

2 participants