Replies: 1 comment
-
Probably what you are looking for is
This is already planned, but in a slightly different way. We are planning to split
Then, after this, we will make We've already done
Sure.
Let's hold on this one. Yes. Most of the commands are anyway under As you found out, aliasing as a git subcommand is something we suggest (https://docs.aviator.co/aviator-cli/how-to-guides/git-subcommand-aliasing). I, for example, set
This is done at #271.
This is also planned. |
Beta Was this translation helpful? Give feedback.
-
Firstly thank you so much for making this tool. I think it's great. I've been using it for a couple of days and have these suggestions that I think could really help with the workflow. Was unsure if this was the best place to post it, feel free to let me know if not and I will move it.
Allow
av stack sync
to be ran at the root of the repoReason: So you can sync all your stacks in one go rather than having to do them individually. Additionally you would be able to easily clean up all merged branches with
--prune
in one goMake
av stack sync
run --trunk, --prune, by default in an interactive wayFor example:
av stack sync
Branch X has been merged do you wish to delete this branch y/n
This stack is behind your main branch do you wish to sync to the trunk y/n
Reason: it would keep the repo clean with less conscious effort to run prune and trunk commands
Make
av stack submit
check if the stack needs syncing before pushingFor example:
av stack submit
Your branch X has fallen behind its parent, do you want to restack before submitting y/n
Reason: stops out of data PRs from being created
Improvements to navigating around stacks (Done)
Make(done feat: allowav stack prev
move to trunk when at the bottom of the stack rather than erroringstack prev
to move to the trunk of the stack #317)Addav stack top
andav stack bottom
for moving to either end of the stack quicklyav stack next --last
so this isn't requiredMake(done Add interactiveav stack next
let you select when there are multiple optionsstack next
#303)Add top level aliases for common commands
For example:
av next
->av stack next
av prev
->av stack prev
av submit
->av stack submit
av modify
->av commit amend --no-edit
av amend
->av commit amend
ac create
->av stack branch
Reason: better out of box experience, faster to preform these common actions - I realise I could make these with git aliases (and I have), but would be great if they were out of the box
Automatically outline the PR stack in the PR description(Done)For example:👉🏻 #1234 feat: adding the component#1235 feat: wiring it up to the backend#1236 feat: adding to correct pagesAdd
av stack absob
similar to git-absorb or sapling absorbBeta Was this translation helpful? Give feedback.
All reactions