renaming VS hub

Uh, no. This is false. It’s just part of a broader trend to stop using ‘master’ due to some people finding that term offensive.

https://github.com/github/renaming

There's a standard GitHub uses for license files (which must be at the root of the repo) which fills in the "license" field on the right column of the repo. If the standard isn't met then the link just says "View license". I imagine TabNine is pulling the license from the GitHub API.

https://docs.github.com/en/repositories/managing-your-reposi...

https://github.com/Vedenin/useful-java-links

When master branch is renamed to main, GitHub redirects any old links. https://github.com/github/renaming#renaming-existing-branche...

Github did something similar in 2020: https://github.com/github/renaming

When you initialize a new Git repository, you will have an initial branch created for you. The default branch name is "master"; because of the negative association with this word, that is bound to change soon — many organizations in the Git ecosystem, like GitHub or GitLab, are replacing "master" with "main".

Github is making it easier for you to change the default branch of your repository. Check out their recommendations for renaming your default branch.

GitHub benennt 'master' zu 'main' um - obwohl 'master' dete halt vo 'master copy' chond.

The function can take a second optional argument to change its behavior. For instance, if your repository default branch is main instead of master (GitHub’s new default), you’ll need to add default_branch: 'main':

fyi github themself didn't really care about this--despite they made github/renaming repo. these repo below are using "master" as the default branch, sorted descending by star count,

I am not actually familiar with anyone who I believe is offended or excluded, but GitHub has put out a lot of information on the topic (https://sfconservancy.org/news/2020/jun/23/gitbranchname/ , https://stackoverflow.com/questions/64249491/difference-between-main-branch-and-master-branch-in-github ) and I am the kind of person to save every keystroke possible so just for that reason I'm not against it.

Try automating the PR process as much as possible. Make use of tools like hub CLI for speeding up the pull request process. Code quality tools can help you automate the due diligence for coding standards and conventions, and test automation tools can assist in bug discovery, and identifying security vulnerabilities.

parse_git_branch() { # Speed up opening up a new terminal tab by not # checking `$HOME` ...which can't be a repo anyway # # For the heck of it, micro-optimize this too: # time (repeat 1000000 { [ "$PWD" = "$HOME" ] } ) == ~4.2s # time (repeat 1000000 { [[ "$PWD" == "$HOME" ]] } ) == ~1.4s [[ "$PWD" == "$HOME" ]] && return # Fastest known way to check the current branch name # (Uses `command` to bypass wrappers like https://hub.github.com/) ref="$(command git symbolic-ref --short HEAD 2> /dev/null)" || return echo " [$ref]" }

Which will create a new remote with that name (otherwise origin will be used).

It is also less typing.

[1]: https://github.com/github/hub

I alias git to use HUB from GitHub

If you also install Hub https://github.com/github/hub it gives you a git create command, it also has a set of really useful additional CLI utilities.

SCM: Git + Hub (https://github.com/github/hub)

This is my favorite feature of this tool. Because every time I commit something and want to create PR/MR, I have to do a bunch of repetitive clicks here and there. On top of that, sometimes I have to work with GitHub, sometimes GitLab. So even if I wanna use the GitHub CLI tool hub or GitLab CLI tool glab, I am ending up using two different tools. So it's nice when I can open PR/MR just by a shortcut within a second or two regardless of what SCM I am on.

Hub - a wrapper for Git command (Git+Hub=GitHub).