I’ve approved it, you can merge whenever you’re ready. Then you’ll have created your first new piece of Exercism: congratulations, and thank you!
A bit more on Git/GitHub (usually abbreviated GH).
It is good to learn how to use basic Git from the command line. That is knowledge that stays valuable.
If you prefer, there is GitHub Desktop. And if you DO want to work from the terminal, but want the extra features there is also GitHub CLI.
I’m not the best person to advise on the relative merits of these. For odd, historical reasons, I use GitKraken Desktop, which costs $$ and is ridiculous overkill for my needs (or yours).
Someone is telling me git command for the “squash merge” would be git merge --squash say followed by git commit… Would that be safe to try at this juncture?
You can always make a new branch based on the current one to test things out.
You don’t need to squash commits; that is typically done when the PR is merged.
If you don’t see the green button on the GH website, it’s because you don’t have write access to the main branch. Exercism protects that: even most maintainers need a different maintainer to approve their PRs.
I misled you yesterday (unintentionally!) by suggesting you would be able to merge once I’d approved. Well, we’re all learning…
Auto-close for PRs should now be disabled on the R track, removing one barrier to contributions.
I just re-read our instructions for new contributors here, and there is a broken link to the contributing guide. @frequenter, now that you are an experienced R contributor, would you be interested in fixing this?
On line 30, it says
As a first step we recommend you read the [contributing guide](https://github.com/exercism/docs/blob/master/contributing-to-language-tracks/README.md).
I think the link in parens should be
https://exercism.org/docs/building
Your choice, but the fix is useful, practice is useful, and you get rep for this…
If you PR it, I’ll approve and merge. As I said, I can’t approve my own PRs but yours are OK.
Just a “git nugget” here: More recently git switch is available and likely less confusing to use if you start to look at the options available for both.
Feel free to ignore this message, though, but I noticed that git is a pretty large topic of discussion here so thought it would be helpful as a note.
I’ve never heard of git switch before :D Thanks! git got a lot of commands and I just know a few basic commands.
Realistically, practically, you only need to know a few commands to be useful/dangerous. Similar to Vi/Vim.