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

util: show all dirty status indicators #349

Closed
wants to merge 2 commits into from
Closed

Conversation

vegerot
Copy link
Contributor

@vegerot vegerot commented Dec 23, 2022

Summary: Instead of just showing ? or *, show one of each symbol in the
dirty status. This means there will be a maximum of 5 characters at the end of
the prompt, which is fine.

Test Plan: blocked by #447

Question for reviewer: I am having trouble running the test suite for Sapling.
I'd appreciate some help getting this working. I can provide more details if
you wouldn't mind helping

@vegerot
Copy link
Contributor Author

vegerot commented Dec 24, 2022

This PR got borked somehow :/ #350

@vegerot vegerot force-pushed the pr349 branch 2 times, most recently from 56e71e0 to b84d503 Compare January 11, 2023 18:51
Summary: Add shell prompt for Sapling.  The current prompt only supports git
and hg, but not sl.  Since the `hg` prompt should work the same for `sl`, use
`_hg_prompt` for Sapling if a `.sl` directory exists

Test Plan: Blocked by facebook#447
TODO: copy `.hg` testcases from `eden/scm/tests/test-fb-ext-scm-prompt-hg.t`
@bolinfest
Copy link
Contributor

@vegerot I can close this one, right?

@vegerot vegerot changed the title placeholder for pull request util: show all dirty status indicators Jan 19, 2023
@vegerot
Copy link
Contributor Author

vegerot commented Jan 19, 2023

@bolinfest you can close it if you don't want this feature 🙂

The PR message got messed up because of #350. I manually copy/pasted the commit info into the PR.

At least I would like to see the first commit in this stack merged in #348

Summary: Instead of just showing `?` or `*`, show one of each symbol in the
dirty status.  This means there will be a maximum of 5 characters at the end of
the prompt, which is fine.

Test Plan: blocked by facebook#447

Question for reviewer: I am having trouble running the test suite for Sapling.
I'd appreciate some help getting this working.  I can provide more details if
you wouldn't mind helping
@facebook-github-bot
Copy link
Contributor

@quark-zju has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

facebook-github-bot pushed a commit that referenced this pull request Feb 15, 2023
Summary:
util: add zsh prompt

 Add shell prompt for Sapling.  The current prompt only supports git
and hg, but not sl.  Since the `hg` prompt should work the same for `sl`, use
`_hg_prompt` for Sapling if a `.sl` directory exists

Pull Request resolved: #348

Test Plan:
Blocked by #447
TODO: copy `.hg` testcases from `eden/scm/tests/test-fb-ext-scm-prompt-hg.t`

 ---
Stack created with [Sapling](https://sapling-scm.com). Best reviewed with [ReviewStack](https://reviewstack.dev/facebook/sapling/pull/348).
* #349
* __->__ #348

Reviewed By: genevievehelsel

Differential Revision: D43326422

Pulled By: quark-zju

fbshipit-source-id: 3ceaf037ce62a06455c60a7e3669ec99c9428c5d
facebook-github-bot pushed a commit that referenced this pull request Aug 1, 2024
Summary: Pull Request resolved: facebook/mvfst#349

Reviewed By: vitaut

Differential Revision: D60154344

fbshipit-source-id: dfadbf0a7e01867875c00b244857a560bc3497ad
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants