Skip to content

Conversation

@yashNaN
Copy link
Contributor

@yashNaN yashNaN commented May 30, 2025

Can now do stacky commit -am "message" to add all files and then commit

yashNaN and others added 3 commits August 1, 2024 13:56
For many repositories it is possible to have more than one base branch we want to work off of. For instance if you have a release branch that you don't want to rebase into main but want to work on the release branch. You should be able to have multiple bottom branches in a repo.

stacky upstack as bottom will change the current branch to be a bottom branch. We will track all non master branches with a new ref refs/stacky-bottom-branch/branch-name. A bottom branch cannot be restacked onto something else, but another bottom branch can adopt a bottom branch to bring it back into a stack.

stacky update will also now clean up unused refs.

Tested using
git co test_1  && stacky.py branch new test_2 && stacky.py upstack as bottom &&  stacky.py info
stacky update
stack restack onto master for a bottom branch
stacky adopt
stacky info --pr



Stacky should work just fine with either rebasing or git merging.

This makes a change that adds a [GIT] section to the stacky config and 2 settings use_merge and use_force_merge to change to merge commits and disallowing force pushes. If we disallow force pushes and want to use merging we should also disallowing amending commits, which this pr does.

Sample ~/.stackyconfig with these changes set
```
  [UI]
  change_to_main = True
  
  [GIT]
  use_merge = True
  use_force_push = False
```
---------

Co-authored-by: Yashwanth Nannapaneni <[email protected]>
@mpatou-openai
Copy link

Pr is failing some tests @yashNaN it seems.

@mpatou-openai
Copy link

Hum ok it's the XAR stuff ...

#3)

* New command stacky branch commit which will create a branch and commit

* Updating readme for stacky branch commit
@yashNaN
Copy link
Contributor Author

yashNaN commented Jun 3, 2025

What's the XAR stuff?

yashNaN and others added 23 commits June 2, 2025 20:46
…sed or failed for a pr (#6)

* Adding functionality to stacky inbox to alsio list if checks have passed or failed for a pr

* Fixing new line when not displaying checks

* Cleaning up some stuff with inbox

---------

Co-authored-by: Yashwanth Nannapaneni <[email protected]>
Adding a command to allow folding the current branch into it's parent
branch. All children branches of my current
branch will become children of the parent

Also fixing issue where use_merge was overwritten

---------

Co-authored-by: Yashwanth Nannapaneni <[email protected]>
Co-authored-by: Yashwanth Nannapaneni <[email protected]>
Adding new command stacky pr, which will list all of the current users
PRs and let you interactively update descriptions

Co-authored-by: Yashwanth Nannapaneni <[email protected]>
Adding a comment to the pr description showing the current stack

Co-authored-by: Yashwanth Nannapaneni <[email protected]>
…se_merge or not (#19)

Co-authored-by: Yashwanth Nannapaneni <[email protected]>
Including the entire forest in stacky comment for a PR rather than just the linear path to the stack bottom
Updated emoji logic match stacky inbox categorization:
    - 🚧 Construction for draft PRs (work in progress)
    - ✅ Check-mark for approved PRs
    - 🔄 Loading for PRs waiting on review (has pending review requests)
    - ❌ X for PRs waiting on author action (no pending reviews, likely needs changes)
…n compact_pr_display to for stacky info --pr to be more compact (#24)

Co-authored-by: Yashwanth Nannapaneni <[email protected]>
Adding a new enable_stack_comment setting to enable/disable stacky stack comment
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants