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

Create a simpler deployment process #1030

Closed
michplunkett opened this issue Aug 21, 2023 · 0 comments · Fixed by #1064
Closed

Create a simpler deployment process #1030

michplunkett opened this issue Aug 21, 2023 · 0 comments · Fixed by #1064
Assignees

Comments

@michplunkett
Copy link
Collaborator

What issue are you seeing?

We currently put all changes to the develop branch, merge the changes we want into main, create a tag on main, and then merge that back into develop. Since we are making use of squash-commits, each commit to develop is a discrete feature, and ALL commits are approved by at least one person, I'd propose that we just create tags off of develop. This way we could make our process one step as oppose to four highly redundant steps.

@abandoned-prototype abandoned-prototype self-assigned this Sep 22, 2023
@michplunkett michplunkett linked a pull request Sep 22, 2023 that will close this issue
3 tasks
abandoned-prototype added a commit that referenced this issue Sep 23, 2023
## Fixes issue
#1030

## Description of Changes
Previously a push on the main branch triggered a deploy to prod. In the
future, creating a release will trigger that push.
The change is already built in a way that we can delete the main branch
and rename the develop branch to main as a next step (once we confirmed
everything works).
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 a pull request may close this issue.

2 participants