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

Semantic branch shortening #728

Open
nojhan opened this issue Aug 16, 2022 · 1 comment
Open

Semantic branch shortening #728

nojhan opened this issue Aug 16, 2022 · 1 comment
Labels
enhancement Feature request needs information More information needed from the reporter

Comments

@nojhan
Copy link
Collaborator

nojhan commented Aug 16, 2022

Allow to shorten long VCS branch names.

Description

Basics: if the branch name is too long, shorten it:

  • fix-stuff-for-pre-release -> fix-stuff…release

Advanced: shortening takes into account semantic branch naming (i.e. preserve the type and the target).

  • fix(frontend)-this-bug -> fix(stuff)…-bug
@nojhan nojhan added the enhancement Feature request label Aug 16, 2022
@Rycieos
Copy link
Collaborator

Rycieos commented Aug 21, 2022

This is a good idea, but it will need a lot of work. Path shortening is by far the most complicated part of Liquidprompt, and I expect this to be quite complicated as well.

Probably should be configurable with the maximum length like LP_PATH_LENGTH.

Maybe we should throw out more examples, which can serve as both test cases as well as user stories for how we want this to work. And also just more user stories.

I'll start:

bugfix/a-weird-bug-i-once-found -> bugfix/…once-found  # keep everything up to the slash regardless.
feature/#728-semantic-branch-shortening -> feature/#728…  # maybe the beginning of the branch is more helpful.

@Rycieos Rycieos added the needs information More information needed from the reporter label Aug 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Feature request needs information More information needed from the reporter
Projects
None yet
Development

No branches or pull requests

2 participants