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

Fix/refactor deployment #351

Merged
merged 3 commits into from
Apr 2, 2024
Merged

Fix/refactor deployment #351

merged 3 commits into from
Apr 2, 2024

Conversation

warrensbox
Copy link
Owner

Planning to remove the "release" branch.

  • With the new setup, we do not have to merge to "release" to deploy the new code.
  • We can constantly push to master and release it bi weekly
  • This will make iteration faster
  • It has alway been a hassle managing the release banch
new-release-example-ezgif.com-video-to-gif-converter.mov

Copy link
Collaborator

@yermulnik yermulnik left a comment

Choose a reason for hiding this comment

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

LGTM

@yermulnik
Copy link
Collaborator

@warrensbox Leaving this to you to get it merged so that I don't step your toes.

@yermulnik yermulnik linked an issue Apr 2, 2024 that may be closed by this pull request
@warrensbox warrensbox merged commit c9f4cd8 into master Apr 2, 2024
2 checks passed
@warrensbox warrensbox deleted the fix/refactor-deployment branch April 2, 2024 18:06
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.

Use default branch for releases instead of release branch
2 participants