I'm a beginner at Git.
I've studied SourceTree before (complicated and frustrated)
If you try using GitHub Desktop again,
"Fetch pull push is aggregated into one button"
There is no tree-shaped visuals, etc.
The concept is fairly simplified and
It's like just making, committing, and pushing a branch (without even thinking about the tree).
Can you finally use it?I feel it now.
Conversely,
ブランチYou cannot check out except for branches (tags, HEADs, past commits) br
"No tree shape"
"There is no button to call the terminal."
and so on.
"Simplified because GitHub's minimal functionality (such as Pullik) works well without using it."
Am I correct in understanding that (I would like to know if I should expand my study range or if I should proceed as it is.)
Or, "It's just that the development of GitHub Desktop is not keeping up.
With minimal functionality (I think it depends on the field as well)But honestly, I can't use it in practice, so I need to use the terminal and other GUI tools."
Is that the way it is?
Avoid answering in that direction because it is difficult for developers to objectively evaluate whether a software is acceptable for use, and answer what purpose GitHub Desktop is being developed and how it will be developed in the future.
GitHub Desktop has published an official document from which to quote.
https://github.com/desktop/desktop/blob/development/docs/process/what-is-desktop.md
3.GitHub Desktop priorities workflows for beginners and collaborative teams.
We want to create an inclusive and approachable way for developers to turn ideas into reality, and we see GitHub Desktop as critical in reducing the intimidation of working with Git on the command line. Users of all experience levels will continue to benefit from GitHub Desktop’s features but when we have to choose between workflows for advanced Git users and workflows for beginner Git users, we prioritize beginners. Additionally, we think it’s foundational to support solo development, but our unique value comes from combining the power of GitHub with the convenience of working locally so that you can collaborate with your team easily. This also means GitHub Desktop will likely not support workflows that are unique to your team, against documented best practice, or different from the vast majority of developers.
"Especially, I think the ""we prioritize beginners"" part is helpful."In other words, it is designed to be easy for everyone using GitHub, but it is easier for beginners to use git than for people who can already use git flexibly in terminals.
Supplement: If you want a more specific answer to your methodology or design philosophy, it's easier to write an answer like "How do I do ○○ on GitHub Desktop?" or "I can do that," "I haven't implemented it yet, but I don't think it's going to be implemented for this reason."
I think GitHub Desktop is a tool with a history of development, so it's not like "development is not keeping up" but
"The design concept seems to be ""minimum functionality required."""
It depends on each person what and how far they want the tool, but I use GitKraken as Git's GUI client.There are more things I can do than GitHub Desktop, but I personally use it to display commit graphs, and it's actually a command line operation.
It's not much different from what you've already answered, and it's almost like a snake's foot.
@nekketsuuuu I think it would be a good idea to look at the entire introduction page through Google translation.
Among them, the following sentence is the shortest answer to the question.
In other words, not all functions and requirements can be achieved with a single software.
(Bold text quoted)
GitHub Desktop is not a replacement for the functionality of Git, but a tool to enable you and your team to be more productive.
GitHub Desktop is not an alternative to Git's capabilities, but a tool to increase productivity for you and your team.
© 2024 OneMinuteCode. All rights reserved.