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

Main2Dev @W-16095971@ Merging main to dev after v1.0.0 #113

Merged
merged 4 commits into from
Jul 30, 2024
Merged

Conversation

svc-cli-bot
Copy link
Collaborator

This branch and PR were automatically created following the successful release of v1.0.0.
It must be MERGED into dev, NOT SQUASHED OR REBASED. Squashing or rebasing this branch onto dev can cause potentially irreconcilable merge conflicts later.
As an additional safeguard and reminder, the title of this PR MUST include the word 'merging' in the description portion of the PR title, e.g., 'Main2Dev @w-xxxxxx@ Merging main to dev after vX.Y.Z'.
If there are conflicts between dev and this branch, you should do the following locally:

  • $ git checkout dev
  • $ git pull
  • $ git fetch --all
  • $ git checkout m2d/v1.0.0
  • $ git pull origin dev --no-rebase # You MUST include this flag, or someone's day will be ruined.
  • Resolve the merge conflicts manually. When in doubt, ask the code's author for help.
  • $ git commit
  • $ git push

@jfeingold35 jfeingold35 changed the title Filler title. Read description and rename. Main2Dev @W-16095971@ Merging main to dev after v1.0.0 Jul 30, 2024
@jag-j jag-j self-requested a review July 30, 2024 17:40
@jfeingold35 jfeingold35 merged commit 5d043e0 into dev Jul 30, 2024
12 of 13 checks passed
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.

3 participants