-
Notifications
You must be signed in to change notification settings - Fork 9
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: Rename dev
branch to main
#2202
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
actions
Related to GitHub Actions workflows
tests
Related to automated testing (unit, UI, integration, etc.)
labels
Jul 5, 2024
lalver1
force-pushed
the
refactor/rename-dev-to-main
branch
2 times, most recently
from
July 8, 2024 22:16
838ff32
to
9e93b75
Compare
thekaveman
requested changes
Jul 8, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking really good 👍 I have just a couple of comments on a few different areas, we can talk through anything as needed at our pairing session.
lalver1
force-pushed
the
refactor/rename-dev-to-main
branch
from
July 9, 2024 15:23
9e93b75
to
305aaec
Compare
angela-tran
reviewed
Jul 9, 2024
lalver1
force-pushed
the
refactor/rename-dev-to-main
branch
from
July 9, 2024 19:20
305aaec
to
fb33b96
Compare
thekaveman
requested changes
Jul 9, 2024
lalver1
force-pushed
the
refactor/rename-dev-to-main
branch
from
July 9, 2024 19:52
fb33b96
to
68a924c
Compare
thekaveman
approved these changes
Jul 9, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR implements the first step of code changes needed to transition the
benefits
repository to tag-based deployments as described in #1527. The code changes are associated with:dev
in the documentation or code commentsTo merge these code changes:
dev
branch tomain
in the repository's settings. Renaming instead of creating a new branch avoids having to set up branch protection rules again formain
.main
environment in GitHub’s Environments settings page following the same configuration as thedev
environmentAZURE_WEBAPP_PUBLISH_PROFILE
AZURE_WEBAPP_NAME
main
.Notes
These may be helpful when reviewing workspace.py:
REASON
=Build.Reason
: The event that caused the build to run.OTHER_SOURCE
=System.PullRequest.SourceBranch
: The branch that is being reviewed in a pull request.INDIVIDUAL_SOURCE
=Build.SourceBranchName
: The name of the branch in the triggering repo the build was queued for.TARGET
=System.PullRequest.TargetBranch
: The branch that is the target of a pull request.