You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be wonderful if we could run Grace side-by-side with Git in the same repository, and have Git not notice Grace's presence (and vice-versa).
This would enable us to scale up real-world testing of Grace, with no risk to the user. In that directory, Git would still be the official VCS (until it's not), and users would run Grace in that directory at the same time, using Grace the way they'd use it if it were the real VCS.
I'm not sure this is possible in more than a limited way. We'll run into the Grace/Git impedance mismatch on merges vs. promotions pretty quickly if we try to automate it, and this idea might not be work the work beyond tracking a single developer's local work.
It is worth thinking through more deeply... if we can find a good way, it would be extremely helpful.
Investigate if local git hooks could provide enough fidelity to match with Grace events
Double-check both Git and Grace .ignore files to make sure they're correct
Write instructions
The text was updated successfully, but these errors were encountered:
It would be wonderful if we could run Grace side-by-side with Git in the same repository, and have Git not notice Grace's presence (and vice-versa).
This would enable us to scale up real-world testing of Grace, with no risk to the user. In that directory, Git would still be the official VCS (until it's not), and users would run Grace in that directory at the same time, using Grace the way they'd use it if it were the real VCS.
I'm not sure this is possible in more than a limited way. We'll run into the Grace/Git impedance mismatch on merges vs. promotions pretty quickly if we try to automate it, and this idea might not be work the work beyond tracking a single developer's local work.
It is worth thinking through more deeply... if we can find a good way, it would be extremely helpful.
The text was updated successfully, but these errors were encountered: