![]() ![]() if CI/CD is set PROPER (if a team/user KNOWS what is doing) this would really turn their work from stages into the flow. ![]() We prioritize workflows for members of teams, and pushes often trigger CI, notifications, and other hooks that we want people to have more control over when those things occur." -Īctually we reeal devops here in teams workflows CICD and all want that thing (auto-pushing, - say, once per every 5 minutes project been left intact) intentionally, - you see, when CI starts then it auto-tests all that doodie pushed and traces errors developer have, (maybe even reports them to his supervisor, heh),. "We think it's valuable for users to have control over when they make their code visible to others. We really appreciate the input from everyone - specifically the examples of where this has fallen down for you - and we definitely are interested in making that core problem less acute for folks. Given that we're looking at solving the core problem in other ways, I'm going to remove the future-proposal label. We're looking at addressing this problem in the context of onboarding in #5686, and in a couple open issues centering around the local/remote distinction here #5873 and here #5330 We think there's still value in maintaining that distinction for a variety of reasons, but we definitely think we can improve the ability to visually distinguish between things that are local-only and those that also exist on GitHub. This is also a really interesting problem that gets at the distinction between working locally vs. We prioritize workflows for members of teams, and pushes often trigger CI, notifications, and other hooks that we want people to have more control over when those things occur. We think it's valuable for users to have control over when they make their code visible to others.It renders the "Undo commit" functionality useless because it's already pushed up to the remote.For beginners especially, this could seem like an enticing feature, but potentially puts them in bad spots where they've pushed something they didn't intend to or that they never wanted to be visible to others.There are a couple downsides we see to this feature that makes it feel like a blunt instrument for solving the problem above: "I have to remember to push manually after committing in order to get my code up to GitHub, and if I forget to do so it never gets pushed up." So this wouldn't just be a one to one replacement for that previous feature.įrom reading through this issue and understanding the usage of the feature on the previous Mac app, here's my summary of the problem this is intended to solve: We've also deprecated the "Sync" terminology because of confusion, especially when things go awry in favor of more explicit language that makes it obvious what's occurring. For context, this was previously only in the GitHub for Mac app, not in both. This feature isn't currently on our roadmap and we think focusing on the core problem is more appropriate than implementing this as requested. Thanks to everyone who has provided input on this! Therefore I would suggest that an app called "Github Desktop" should be biased toward one-click Sync and commit-and-push as a conceptual model, rather than adhering strictly to the underlying Git paradigms. I personally don't see the value in local repo's, and one could argue that the entire reason Github exists (central repository) is antithetical to local repo's. Just a weird enough model that lots of people make the mistake of not committing back to the main repo (Github itself). But Github is the odd man out in revision control in that it is a distributed system with local repositories. But project teams often use source code revision control systems for other things like documentation and image assets and the like - which they should: everyone should use it for everything. This is an easy feature, and since you closed it a year ago as "not in roadmap", maybe you could reconsider Git is a programmer's tool in some ways (hence the rationale for not having "convenience features" like this). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |