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

Use default branch for releases instead of release branch #282

Closed
nitrocode opened this issue Dec 19, 2022 · 2 comments · Fixed by #351
Closed

Use default branch for releases instead of release branch #282

nitrocode opened this issue Dec 19, 2022 · 2 comments · Fixed by #351
Assignees
Labels
enhancement Refactor existing code for better performance and quality

Comments

@nitrocode
Copy link

nitrocode commented Dec 19, 2022

Is your feature request related to a problem? Please describe.
Since the default branch is master (older commit) and the release branch is release (latest commit), a renovatebot configuration for atlantis keeps trying to change the dependency to an older commit.

Describe the solution you'd like

  • always merge to default branch and cut releases there instead of from the separate branch release
  • or if the separate branch release is needed then make it default
  • or please provide a renovatebot workaround confirm to track a specific golang dependency (tfswitch) releases from the release branch instead of the default branch

Describe alternatives you've considered
Nome

Additional context

@nitrocode nitrocode added the enhancement Refactor existing code for better performance and quality label Dec 19, 2022
@nitrocode
Copy link
Author

@warrensbox friendly ping. Please consider this change 🙏

@yermulnik yermulnik linked a pull request Apr 2, 2024 that will close this issue
@yermulnik
Copy link
Collaborator

Apparently this #351 is to switch from release to master.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Refactor existing code for better performance and quality
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants