-
Notifications
You must be signed in to change notification settings - Fork 372
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
docs: Add branch tracking to branches.md. #2625
Conversation
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.
Thanks for tackling on this! I've added some inline comments. I think it's better to update branches.md instead of adding new separate page.
Yes, I only noticed branches.md after I started writing. At least for me it's simpler to start from a blank page. I'll move it to the remotes section. |
273cabe
to
69a81a8
Compare
I'm marking this PR as ready for review for any further refinements. |
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.
lgtm, thanks.
nit: the commit message includes WIP: Not done yet
.
9134bff
to
8ccb35f
Compare
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.
Thanks!
I glanced at this, it looks pretty good to me too. I still think we should mention |
Thanks.
I don't mind landing this in the new year. So take your time. |
… help` This tries to clarify the fact that the branches must be remote and the syntax for specifying them as globs. Cc @yuja, jj-vcs#2625 (comment) Here is the result (excerpt): ``` $ jj branch track --help Start tracking given remote branches A tracking remote branch will be imported as a local branch of the same name. Changes to it will propagate to the existing local branch on future pulls. Usage: jj branch track [OPTIONS] <BRANCH@REMOTE>... Arguments: <BRANCH@REMOTE>... Remote branches to track By default, the specified name matches exactly. Use `glob:` prefix to select branches by wildcard pattern. For details, see https://github.com/martinvonz/jj/blob/main/docs/revsets.md#string-patterns. Examples: branch@remote, glob:main@*, glob:jjfan-*@upstream ```
… help` This tries to clarify the fact that the branches must be remote and the syntax for specifying them as globs. Cc @yuja, jj-vcs#2625 (comment) Here is the result (excerpt): ``` $ jj branch track --help Start tracking given remote branches A tracking remote branch will be imported as a local branch of the same name. Changes to it will propagate to the existing local branch on future pulls. Usage: jj branch track [OPTIONS] <BRANCH@REMOTE>... Arguments: <BRANCH@REMOTE>... Remote branches to track By default, the specified name matches exactly. Use `glob:` prefix to select branches by wildcard pattern. For details, see https://github.com/martinvonz/jj/blob/main/docs/revsets.md#string-patterns. Examples: branch@remote, glob:main@*, glob:jjfan-*@upstream ```
8ccb35f
to
2fae523
Compare
@ilyagr PTAL, I took a stab at a "What does |
… help` This tries to clarify the fact that the branches must be remote and the syntax for specifying them as globs. Cc @yuja, #2625 (comment) Here is the result (excerpt): ``` $ jj branch track --help Start tracking given remote branches A tracking remote branch will be imported as a local branch of the same name. Changes to it will propagate to the existing local branch on future pulls. Usage: jj branch track [OPTIONS] <BRANCH@REMOTE>... Arguments: <BRANCH@REMOTE>... Remote branches to track By default, the specified name matches exactly. Use `glob:` prefix to select branches by wildcard pattern. For details, see https://github.com/martinvonz/jj/blob/main/docs/revsets.md#string-patterns. Examples: branch@remote, glob:main@*, glob:jjfan-*@upstream ```
As far as I can see in the chat, there's no objection to changing the default, and git.auto-local-branch = false is generally preferred. docs/branches.md isn't updated as it would otherwise conflict with jj-vcs#2625. I think the "Remotes" section will need a non-trivial rewrite. jj-vcs#1136, jj-vcs#1862
As far as I can see in the chat, there's no objection to changing the default, and git.auto-local-branch = false is generally preferred. docs/branches.md isn't updated as it would otherwise conflict with jj-vcs#2625. I think the "Remotes" section will need a non-trivial rewrite. jj-vcs#1136, jj-vcs#1862
I'd like to land this in the upcoming weeks, ideally before we have a new release. If you have nits or improvements for the new section feel free to add them now. |
2fae523
to
069516e
Compare
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.
Thanks!
Thanks for the reminder, Philip! I added a few suggestions as well; feel free to adjust them further. |
069516e
to
fdfc935
Compare
This tries to explain Jujutsu's branch tracking for a newcomer. It is based on it's design doc in `docs/design/tracking-branches.md`.
fdfc935
to
550e78b
Compare
This follows up on jj-vcs#2625 and updates all sections of `branches.md` to represent the new default of `git.auto-local-branch=false`. I also realized that the paragraph we discussed for so long with @PhilipMetzger actually repeats information that was already present a bit earlier in the file. So, I removed most of it and moved the rest. Sorry I didn't notice this earler.
This follows up on jj-vcs#2625 and updates all sections of `branches.md` to represent the new default of `git.auto-local-branch=false`. I also realized that the paragraph we discussed for so long with @PhilipMetzger actually repeats information that was already present a bit earlier in the file. So, I removed most of it and moved the rest. Sorry I didn't notice this earler.
This follows up on jj-vcs#2625 and updates all sections of `branches.md` to represent the new default of `git.auto-local-branch=false`. I also realized that the paragraph we discussed for so long with @PhilipMetzger actually repeats information that was already present a bit earlier in the file. So, I removed most of it and moved the rest. Sorry I didn't notice this earler.
This follows up on jj-vcs#2625 and updates all sections of `branches.md` to represent the new default of `git.auto-local-branch=false`. I also realized that the paragraph we discussed for so long with @PhilipMetzger actually repeats information that was already present a bit earlier in the file. So, I removed most of it and moved the rest. Sorry I didn't notice this earler.
This follows up on jj-vcs#2625 and updates all sections of `branches.md` to represent the new default of `git.auto-local-branch=false`. I also realized that the paragraph we discussed for so long with @PhilipMetzger actually repeats information that was already present a bit earlier in the file. So, I removed most of it and moved the rest. Sorry I didn't notice this earler.
This follows up on jj-vcs#2625 and updates all sections of `branches.md` to represent the new default of `git.auto-local-branch=false`. I also realized that the paragraph we discussed for so long with @PhilipMetzger actually repeats information that was already present a bit earlier in the file. So, I removed most of it and moved the rest. Sorry I didn't notice this earler.
This follows up on jj-vcs#2625 and updates all sections of `branches.md` to represent the new default of `git.auto-local-branch=false`. I also realized that the paragraph we discussed for so long with @PhilipMetzger actually repeats information that was already present a bit earlier in the file. So, I removed most of it and moved the rest. Sorry I didn't notice this earler.
This follows up on jj-vcs#2625 and updates all sections of `branches.md` to represent the new default of `git.auto-local-branch=false`. I also realized that the paragraph we discussed for so long with @PhilipMetzger actually repeats information that was already present a bit earlier in the file. So, I removed most of it and moved the rest. Sorry I didn't notice this earler.
This follows up on jj-vcs#2625 and updates all sections of `branches.md` to represent the new default of `git.auto-local-branch=false`. I realized that the paragraph we discussed for so long with @PhilipMetzger actually repeats information that was already present a bit earlier in the file. So, I removed most of it and moved the rest. Sorry I didn't notice this earler.
This follows up on jj-vcs#2625 and updates all sections of `branches.md` to represent the new default of `git.auto-local-branch=false`. I realized that the paragraph we discussed for so long with @PhilipMetzger actually repeats information that was already present a bit earlier in the file. So, I removed most of it and moved the rest. Sorry I didn't notice this earler.
This follows up on jj-vcs#2625 and updates all sections of `branches.md` to represent the new default of `git.auto-local-branch=false`. I realized that the paragraph we discussed for so long with @PhilipMetzger actually repeats information that was already present a bit earlier in the file. So, I removed most of it and moved the rest. Sorry I didn't notice this earler.
This follows up on jj-vcs#2625 and updates all sections of `branches.md` to represent the new default of `git.auto-local-branch=false`. I realized that the paragraph we discussed for so long with @PhilipMetzger actually repeats information that was already present a bit earlier in the file. So, I removed most of it and moved the rest. Sorry I didn't notice this earler. ## The callout Unfortunately, GitHub and MkDocs use different syntax for admonitions. The callout looks like this in MkDocs: https://github.com/martinvonz/jj/assets/4123047/45d79e7a-35db-492e-a227-004b7e3383c1 Use `poetry run -- mkdocs serve` to double-check.
This follows up on jj-vcs#2625 and updates all sections of `branches.md` to represent the new default of `git.auto-local-branch=false`. I realized that the paragraph we discussed for so long with @PhilipMetzger actually repeats information that was already present a bit earlier in the file. So, I removed most of it and moved the rest. Sorry I didn't notice this earler. ## The callout Unfortunately, GitHub and MkDocs use different syntax for admonitions. The callout looks like this in MkDocs: https://github.com/martinvonz/jj/assets/4123047/45d79e7a-35db-492e-a227-004b7e3383c1 Use `poetry run -- mkdocs serve` to double-check.
This follows up on jj-vcs#2625 and updates all sections of `branches.md` to represent the new default of `git.auto-local-branch=false`. I realized that the paragraph we discussed for so long with @PhilipMetzger actually repeats information that was already present a bit earlier in the file. So, I removed most of it and moved the rest. Sorry I didn't notice this earler. ## The callout Unfortunately, GitHub and MkDocs use different syntax for admonitions. The callout looks like this in MkDocs: https://github.com/martinvonz/jj/assets/4123047/45d79e7a-35db-492e-a227-004b7e3383c1 Use `poetry run -- mkdocs serve` to double-check.
This follows up on jj-vcs#2625 and updates all sections of `branches.md` to represent the new default of `git.auto-local-branch=false`. I realized that the paragraph we discussed for so long with @PhilipMetzger actually repeats information that was already present a bit earlier in the file. So, I removed most of it and moved the rest. Sorry I didn't notice this earler. ## The callout Unfortunately, GitHub and MkDocs use different syntax for admonitions. The callout looks like this in MkDocs: https://github.com/martinvonz/jj/assets/4123047/45d79e7a-35db-492e-a227-004b7e3383c1 Use `poetry run -- mkdocs serve` to double-check.
This follows up on #2625 and updates all sections of `branches.md` to represent the new default of `git.auto-local-branch=false`. I realized that the paragraph we discussed for so long with @PhilipMetzger actually repeats information that was already present a bit earlier in the file. So, I removed most of it and moved the rest. Sorry I didn't notice this earler. ## The callout Unfortunately, GitHub and MkDocs use different syntax for admonitions. The callout looks like this in MkDocs: https://github.com/martinvonz/jj/assets/4123047/45d79e7a-35db-492e-a227-004b7e3383c1 Use `poetry run -- mkdocs serve` to double-check.
This tries to explain Jujutsu's branch tracking for a newcomer.
It is based on it's design doc in
docs/design/tracking-branches.md
.I'd like to have some opinions on it, before finishing it.
cc @yuja, @ilyagr
Checklist
If applicable: