I am sorry, maybe I am a boomer but I don't like it one bit.
> Grace is a new, modern, cloud-native version control system.
The whole point of git was to replace crappy centralized solutions
> Grace Server scales up by running on Kubernetes and massive PaaS services from large cloud providers.
word salad
> Every save is uploaded, automatically
Can't wait for the passwords to start leaking.
Grace simplifies this by breaking these usages out into their own gestures and events:
> grace checkpoint - this means "I'm partially done", for you to keep track of your own progress
> grace commit - this is "I'm really done" or "This version is a candidate for promotion"; you'd use a commit for a PR
> grace promote - in Grace, promotions replace merges; a promotion is how Grace moves code from a child branch to a parent branch
I have no problem with this, I even like it.
Some around here will remember before "MRs", well then called "PRs" were ubiquitous, Git can provide different workflows. We can write tools on top of git, like github, to do more fancy things. I think it's high time for some new concepts backed by git
> When your parent branch gets updated, within seconds, grace watch will auto-rebase your branch on those changes, so you're always coding against the latest version that you'll have to promote to.
I don't think I ever wanted to auto rebase on every time I save. In fact, I think I really don't like this... in fact, we might as well just all start co-editing on the same server
> Personal branches, not forks
> With Grace, there's no need for forking entire repositories just to make contributions. In open-source repos, you'll just create a personal branch against the repo.
This is what everyone does normally, except Github made forks a thing or whatever so you could clone someone elses repo and hack on it without having mainline permissions.
> Personal branches, not forks > With Grace, there's no need for forking entire repositories just to make contributions. In open-source repos, you'll just create a personal branch against the repo.
> This is what everyone does normally, except Github made forks a thing or whatever so you could clone someone elses repo and hack on it without having mainline permissions.
Yeah. I'm an open-source maintainer and the "everyone creates a branch on upstream" model is a complete non-starter for me, even if only due to the mess it would cause. This is a massive step backward from "fork and pull."
> Grace is a new, modern, cloud-native version control system.
The whole point of git was to replace crappy centralized solutions
> Grace Server scales up by running on Kubernetes and massive PaaS services from large cloud providers.
word salad
> Every save is uploaded, automatically
Can't wait for the passwords to start leaking.
Grace simplifies this by breaking these usages out into their own gestures and events:
> grace checkpoint - this means "I'm partially done", for you to keep track of your own progress > grace commit - this is "I'm really done" or "This version is a candidate for promotion"; you'd use a commit for a PR > grace promote - in Grace, promotions replace merges; a promotion is how Grace moves code from a child branch to a parent branch
I have no problem with this, I even like it.
Some around here will remember before "MRs", well then called "PRs" were ubiquitous, Git can provide different workflows. We can write tools on top of git, like github, to do more fancy things. I think it's high time for some new concepts backed by git
> When your parent branch gets updated, within seconds, grace watch will auto-rebase your branch on those changes, so you're always coding against the latest version that you'll have to promote to.
I don't think I ever wanted to auto rebase on every time I save. In fact, I think I really don't like this... in fact, we might as well just all start co-editing on the same server
> Personal branches, not forks > With Grace, there's no need for forking entire repositories just to make contributions. In open-source repos, you'll just create a personal branch against the repo.
This is what everyone does normally, except Github made forks a thing or whatever so you could clone someone elses repo and hack on it without having mainline permissions.