arxanas

12 ms·

91.
by arxanas 4y ago
Yes, in my preferred workflow, I usually create a temporary commit and then switch away. Sapling also has `sl shelve` as `git stash`. If you want to run tests on commits without checking them out, you might want to try my `git test` command
92.
by arxanas 4y ago
Instead of `git add -p`, you would use `sl commit -i` (whose interface I much prefer). To amend into a previous commit, I prefer to switch to it and then just use `sl amend` (+ `sl restack` if necessary), but you can also use `sl fold` IIRC
93.
by arxanas 4y ago
In those cases, I find it best to either 1) use the interactive commit tool to not commit debug junk, or 2) put the debug junk in its own commit, which I'll later discard (and, plus, that means you can't accidentally include it in
94.
by arxanas 4y ago
To use a similar featureset but in the same Git repository you normally use, you can try my https://github.com/arxanas/git-branchless . Then, you can use your usual staging workflows if desired, or use regular Git comma
95.
by arxanas 4y ago
It has an interactive commit staging command which accomplishes the same thing. In that case, it unifies the staging area with regular commits, which means you can also manipulate them the same way as regular commits. AFAICT there are only
96.
Playing Elden Ring in the Cloud(blog.waleedkhan.name)
2 points by arxanas 4y ago|0 comments
97.
by arxanas 4y ago
Keep in mind that under equal temperament, used ubiquitously today, all keys sound the same. The descriptions in the article probably only apply to a certain other tuning system. See https://en.wikipedia.org/wiki/Key_(m
98.
by arxanas 4y ago
Here is a blog post I wrote on the topic https://blog.waleedkhan.name/getting-a-job-in-pl/
99.
by arxanas 4y ago
I (and many developers I know) would use the GitHub individual commit review system, but it has a lot of missing features which make it unreasonable to update commits in the PR. For example, if you rewrite one of the commits in a multi-comm
100.
by arxanas 4y ago
One nice feature of git-branchless (I'm the author) is in-memory rebases. For example, the `git sync` command will rebase all local work on top of the main branch without checking out those branches. (It will also not start merge confl
101.
by arxanas 4y ago
Right, in this case, I would prefer 10 separate review events. Other than for code review purposes themselves, I would want CI to run on each of these commits individually, rather than only on the result at the end.
102.
by arxanas 4y ago
I see, thanks for the information. I often stack 10+ commits, so I don't think your workflow would be reasonable for me. (For example, here, I have 11 finished commits and 3 in progress: https://github.com/arxanas/
103.
by arxanas 4y ago
> Probably some arcane git magic to (interactively) rebase branch There is not really a command for that yet, short of adding a bunch of `exec` steps to your interactive rebase manually. See https://news.ycombinator.com/i
104.
by arxanas 4y ago
Which Git client do you use, and also, how do you remember all the remote branch names? > And even the "long version" is pretty negligible (like, maybe 10 seconds per branch?) I notice that mainly the differences in opinion wit
105.
by arxanas 4y ago
Basically: you don't :) I've only ever found this workflow to work if you can attach multiple commits/code reviews to single higher-level work items in your project management software. There's simply too much overhead i
106.
by arxanas 4y ago
You might be interested in https://github.com/gitext-rs/git-stack , which perfectly implements your workflow where you only put up one PR but continue to work locally on the next commits. > ppl go dark for a month bu
107.
by arxanas 4y ago
Hi bvrmn, I've been meaning to write a comparison of git-branchless with Stacked Git, as they occupy similar spaces. Can you list some of the features which Stacked Git has which git-branchless might not?
108.
by arxanas 4y ago
> But when you call it "anonymous branching" you lay bare that the only advantage is that you don't need to name your work branch Sure, I'm only responding to what you were saying about "There is no such thing; c
109.
by arxanas 4y ago
I am the author of the linked tool git-branchless. Happy to answer any questions about stacked PR workflows here or on GitHub discussions https://github.com/arxanas/git-branchless/discussions or Discord https:&#x
110.
by arxanas 4y ago
If you work at asynchronous/remote work company, i.e. your coworkers are in different timezones and can't review immediately, what else are you going to do? Put out exactly one code review per day until your feature is fully merge
111.
by arxanas 4y ago
Try out the linked tool git-branchless ( https://github.com/arxanas/git-branchless , I'm the author). It should help you restore Phabricator-like workflows. In particular, check out the `git sync`, `git restack`, an
112.
by arxanas 4y ago
git-branchless author here. By "branchless", I mean literally using detached HEAD as the primary state of development. If you're using tools like Gerrit or Phabricator, you never have to explicitly make a branch to get your c
113.
by arxanas 4y ago
The linked tool git-branchless handles this pretty well ( https://github.com/arxanas/git-branchless , I'm the author). You basically run `git checkout <branch>`, `git commit --amend`, and then `git restack`. T
114.
by arxanas 4y ago
Also worth pointing out these commands from git-branchless (I'm the author): - git sync: rebase all commit stacks on top of the main branch. - git restack: run after making a change to a foundational commit to automatically restack dep
115.
by arxanas 4y ago
The mentioned tool `git-branchless` (I am the author) also supports `git prev 3` followed by `git commit --amend`. See https://github.com/arxanas/git-branchless/wiki/Command:-git-...
116.
by arxanas 4y ago
My project https://github.com/arxanas/git-branchless does this. Use `git undo -i` to get a graphical view of where branches were at an arbitrary previous point in time. It's worth noting that, in principle, there
117.
by arxanas 4y ago
You might be interested in my project git-branchless https://github.com/arxanas/git-branchless or the Git-compatible Jujutsu SCM https://github.com/martinvonz/jj , both of which have version contro
118.
by arxanas 4y ago
Try Jujutsu https://github.com/martinvonz/jj
119.
by arxanas 4y ago
Items 2 and 4 are addressed by my git-branchless project: https://github.com/arxanas/git-branchless . You can undo with `git undo`, and merge conflict resolution never starts unless you specify `-m`/`--merge`. Ther
120.
by arxanas 5y ago
I think the contributor graph is misleading, and that he's using git-subtree to vendor tree-sitter, which makes it look like others have contributed more to the project.

More ›