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

chore(dependencies): don't create an autobump PR for halyard on a fro… (backport #1115) #1117

Merged
merged 1 commit into from
Apr 9, 2022

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Apr 9, 2022

This is an automatic backport of pull request #1115 done by Mergify.


Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

  • @Mergifyio refresh will re-evaluate the rules
  • @Mergifyio rebase will rebase this PR on its base branch
  • @Mergifyio update will merge the base branch into this PR
  • @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

  • look at your merge queues
  • generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com

…nt50 release branch (#1115)

since release branches in halyard don't align with release branches in front50.  For
example, a release-1.27.x branch exists in both front50 and halyard.  In front50
release-1.27.x aligns with spinnaker version 1.27.x, but halyard version numbers are
independent from spinnaker versions.

(cherry picked from commit 7fbae17)
@link108 link108 merged commit df87f4c into release-1.28.x Apr 9, 2022
@link108 link108 deleted the mergify/bp/release-1.28.x/pr-1115 branch April 9, 2022 00:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants