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

Document Other User Flows #384

Closed
2 tasks done
CtfChan opened this issue Jan 31, 2025 · 1 comment
Closed
2 tasks done

Document Other User Flows #384

CtfChan opened this issue Jan 31, 2025 · 1 comment
Labels
question Uncertainty is involved

Comments

@CtfChan
Copy link

CtfChan commented Jan 31, 2025

Please complete the following tasks

  • I have searched the discussions
  • I have searched the existing issues

Version

No response

Use Case

Great work with the tool! I was wondering if we should add some documentation around what a users' git-stack workflow might look like. For example,

  • Suppose I have a chain of 3 PRs stacked on top of each other how should I submit them?
  • Supposed I have 3 stacked PRs and I need to make a change for the middle one. How do I go about doing this?

Requirements

No response

Possible Solutions

No response

@CtfChan CtfChan added the question Uncertainty is involved label Jan 31, 2025
@CtfChan CtfChan changed the title Document Submission Flow Document Other User Flows Jan 31, 2025
@epage
Copy link
Collaborator

epage commented Jan 31, 2025

Suppose I have a chain of 3 PRs stacked on top of each other how should I submit them?

This is covered under How do I stack my PRs in Github?

Supposed I have 3 stacked PRs and I need to make a change for the middle one. How do I go about doing this?

Hmm, it looks like we haven't updated the README for git next, git prev, git amend, or git reword (or git run but that is unrelated to this question).

I was wondering if we should add some documentation around what a users' git-stack workflow might look like

An important thing to keep in mind with git stack is that it is meant to complement git workflows, rather than replace. There are also an endless supply of potential workflows for us to cover. I think I'd want to focus on high level details but its really up to the user to then fit the pieces together as they need.

@epage epage closed this as completed in ce0b520 Jan 31, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Uncertainty is involved
Projects
None yet
Development

No branches or pull requests

2 participants