-
For context, I'm in a git co-located project because of #469. My push-to-GitHub flow looks something like this: jbarkhuysen at MacBook-Y9JVN in ~/workspace/cosmos-stratum-htef-runner on (HEAD detached from b013198)*
$ jj
@ ntmxzynt [email protected] 2025-02-11 09:20:02 hidden aea079d2
│ Support for hidden files.
○ qwvwprvv [email protected] 2025-02-11 08:14:08 symlinks2 git_head() 247fbfd4
│ Basic support for symlinks.
○ xqrwzwnr [email protected] 2025-02-11 08:14:08 filerefactor 9e52c8cd
│ Move a few file-y functions to file.go.
◆ tywxkppr [email protected] 2025-02-11 07:15:28 main c62f5451
│ Perform file:// copies after HTEF invocation and add results to FunctionOutputEnvelope. #12
~
# FYI the feature's name is about hidden, it's not semantically meaningful for this issue.
$ git push origin hidden
# This was an accident, but it led to...
$ jj desc
# This locked commits situation:
$ jj
@ yyyomtpm [email protected] 2025-02-11 09:20:40 a256ca50
│ (empty) (no description set)
◆ ntmxzynt [email protected] 2025-02-11 09:20:02 hidden hidden@origin git_head() aea079d2
│ Support for hidden files.
~ (elided revisions)
◆ tywxkppr [email protected] 2025-02-11 07:15:28 main c62f5451
│ Perform file:// copies after HTEF invocation and add results to FunctionOutputEnvelope. #12
~ Why did a Also, how do I get it to stop doing this Thanks for any help. |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 5 replies
-
Bizarrely, if I got to my first in-flight commit $ jj edit filerefactor --ignore-immutable
Working copy now at: xqrwzwnr 9e52c8cd filerefactor | Move a few file-y functions to file.go.
Parent commit : tywxkppr c62f5451 main | Perform file:// copies after HTEF invocation and add results to FunctionOutputEnvelope. #12
Added 0 files, modified 3 files, removed 1 files
$ jj
@ xqrwzwnr [email protected] 2025-02-11 08:14:08 filerefactor 9e52c8cd
│ Move a few file-y functions to file.go.
◆ tywxkppr [email protected] 2025-02-11 07:15:28 main git_head() c62f5451
│ Perform file:// copies after HTEF invocation and add results to FunctionOutputEnvelope. #12
~ Why? 🤨 |
Beta Was this translation helpful? Give feedback.
-
The term for locked commits is "immutable commits". See https://jj-vcs.github.io/jj/latest/config/#set-of-immutable-commits. The default configuration for immutable commits is such that untracked bookmarks are immutable. The elided revisions are configurable by choosing what commits you'd like to display in the default revset: https://jj-vcs.github.io/jj/latest/config/#default-revisions. For example, you could choose to display all commits via |
Beta Was this translation helpful? Give feedback.
-
I think this sort of question is common in the mind of a novice, pointing to needing a bit better defaults or better hints or making the links to docs more prominent...something to help ease the onslaught of new concepts all at once. |
Beta Was this translation helpful? Give feedback.
The term for locked commits is "immutable commits". See https://jj-vcs.github.io/jj/latest/config/#set-of-immutable-commits. The default configuration for immutable commits is such that untracked bookmarks are immutable.
jj bookmark track hidden@origin
should make those commits mutable again. Typically untracked bookmarks correspond to remote bookmarks by other users which you would not typically want to modify.The elided revisions are configurable by choosing what commits you'd like to display in the default revset: https://jj-vcs.github.io/jj/latest/config/#default-revisions. For example, you could choose to display all commits via
all()
.