Closed johnandmegh closed 6 months ago
Git workflow stuff:
rebase
command to organize a pile of commits in a certain way. The most concise explanation I've found is here https://docs.github.com/en/get-started/using-git/about-git-rebaseStyle:
I'll review the content of your changes some time later; I wanted to respond to your questions first.
Thanks very much for the links, I will dig in!
I tried using the GitHub website for these edits because of the easy preview feature, but I'm realizing with so many manipulation pieces using the command line, I should probably be using a cloned repo and the command line?
Yes, almost every guide and doc will assume you are using the cli on a cloned local repo, pushing to some remote like Github.
Many modern editors are git-aware out of the box. For example, if you use vscode, it has a "source control" tab that will do simple git operations for you.
I use the Github editing tools for small one-off edits. As soon as you are editing more than one file, or organizing commits in any way, you will have to get comfortable with the cli
I should add: If you are struggling with something you can always ask for help in the Packaging or Development chat.
Thanks! I think I addressed the wording/consistency issues that you mentioned, and I scanned for similar quotation mark issues in at least the portion included in this request - I'll check the other one I sent as well.
Description
I tried to use some tips on Stack Overflow to "squash" the GitHub commits on my own this time...and somehow I think I made it even messier? (I don't think the end result is changed, but please let me know if I need to go back to the drawing board on how this is submitted)
Also, if this style of update is OK, I could probably tackle the rest of that page - I'm new all of Solus and Budgie, but it seems like a few different settings-related functions got moved from being accessed via Raven to being accessed via the Budgie Menu > Settings? Those would seem easy enough for me to grab new screenshots for and update wording.
Thanks,
Edited a few minutes later: sorry, meant to mention, this is related to #131
Submitter Checklist
git rebase -i
(if needed)