fix: skip pricing confirmation for creating branch#33
Open
sweatybridge wants to merge 3 commits intomainfrom
Open
fix: skip pricing confirmation for creating branch#33sweatybridge wants to merge 3 commits intomainfrom
sweatybridge wants to merge 3 commits intomainfrom
Conversation
sweatybridge
force-pushed
the
skip-prompt
branch
from
9decc04 to
6d8751f
Compare
sweatybridge
changed the title
sweatybridge
force-pushed
the
skip-prompt
branch
from
6d8751f to
e141e06
Compare
sweatybridge
force-pushed
the
skip-prompt
branch
from
e141e06 to
efbbac2
Compare
sweatybridge
changed the title
nareshrajkumar866
approved these changes
May 26, 2025
nareshrajkumar866
approved these changes
May 26, 2025
nareshrajkumar866
approved these changes
May 26, 2025
nareshrajkumar866
approved these changes
May 26, 2025
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
What kind of change does this PR introduce?
chore
What is the new behavior?
creating a new branch
reusing a branch
listing branches
Additional context
Add any other context or screenshots.