3 ms·
About your guess on the Pijul hub: nest.pijul.com does something nicer than PRs, which is to attach changes independent from the context, to discussions. See t
by pmeunier 6y ago
About your guess on the Pijul hub: nest.pijul.com does something nicer than PRs, which is to attach changes independent from the context, to discussions.
See the following discussion, for example: https://nest.pijul.com/pijul/pijul/discussions/104 https://nest.pijul.com/pijul/pijul/discussions/104
These two contributors (@cole-h and @lowenheim) are trying to add colours to the output of `pijul change`, and discuss changes, rewrite them, amend them, push them again. Certainly, some of these changes conflict with others. But that's totally ok, since you can pull them independently.
For example, when preparing release 1.0.0-alpha.9, I didn't pull the latest patch from that discussion into my main local channel, and I preferred to pull some of the older ones instead.
I did this because the latest one doesn't detect whether the standard output is a TTY. If I apply them to the main channel on the Nest, my current local channel will be in sync with it, even though I've worked on ten other features since then.
- rcthompson 6y agoYeah, this is why I talked about a hypothetical "Pijulhub", instead of talking about any real website. The hypothetical website I'm comparing to would be one that replicates Github's features as closely as possible but uses Pijul as the VCS. But as you say, the real answer is that a hub for Pijul should be built around the data model and features of Pijul, not those of Git.