Skip to content

Cursor/single bug resolution ecc9#9053

Open
RajPabnani03 wants to merge 2 commits intojj-vcs:mainfrom
RajPabnani03:cursor/single-bug-resolution-ecc9
Open

Cursor/single bug resolution ecc9#9053
RajPabnani03 wants to merge 2 commits intojj-vcs:mainfrom
RajPabnani03:cursor/single-bug-resolution-ecc9

Conversation

@RajPabnani03
Copy link

Checklist

If applicable:

  • I have updated CHANGELOG.md
  • I have updated the documentation (README.md, docs/, demos/)
  • I have updated the config schema (cli/src/config-schema.json)
  • I have added/updated tests to cover my changes
  • I fully understand the code that I am submitting (what it does,
    how it works, how it's organized), including any code drafted by AI
  • For any prose generated by AI, I have proof-read and copy-edited with an
    eye towards deleting anything that is irrelevant, clarifying anything that
    is confusing, and adding details that are relevant. This includes, for
    example, commit descriptions, PR descriptions, and code comments.

cursoragent and others added 2 commits January 24, 2026 18:01
This fixes issue jj-vcs#8673 where  would fail
because the revset parser did not accept double dashes in bookmark names.

The grammar has been updated to allow:
- Consecutive '-' and '+' characters (e.g., foo--bar, foo++bar, foo+-bar)
- Mixed patterns with '.' (e.g., foo.-bar, foo.+bar)

The '..' sequence is still NOT allowed as part of an identifier because
it's the range operator. So 'foo..bar' is still parsed as a range from
'foo' to 'bar'.

Added tests for:
- Parser-level identifier tests for double/triple dashes
- CLI-level test for git push --named with double dashes

Closes jj-vcs#8673

Co-authored-by: 2020.raj.pabnani <2020.raj.pabnani@ves.ac.in>
Co-authored-by: Raj_Pabnani <RajPabnani03@users.noreply.github.com>
@RajPabnani03 RajPabnani03 requested a review from a team as a code owner March 8, 2026 09:09
Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

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

The following commits do not follow our format for subject lines:

  • 9287d4f: Fix UTF-8 hex escapes in string literals

Commits should have a subject line following the format <topic>: <description>. Please review the commit guidelines for more information.

@google-cla
Copy link

google-cla bot commented Mar 8, 2026

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

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.

2 participants