GitHub common idioms involved in community contributions
PR: Pull Request.
LGTM: Looks Good To Me. Looks good, the code has been reviewed and can be merged.
SGTM: Sounds Good To Me. Similar to the above sentence.
WIP: Work In Progress. If you have a PR that has changed a lot, you can submit it first if you have written a part. Write WIP in the title to tell the project maintainer that this feature has not been completed, which is convenient for the maintainer to review in advance. Partially submitted code.
PTAL: Please Take A Look. Are you here? Used to prompt others to take a look.
TBR: To Be Reviewed. Prompt the maintainer to review.
TL; DR: Too Long; Didn't Read. Too long, not read.
TBD: To Be Done (or Defined / Discussed / Decided / Determined). The meaning differs according to the context, but generally it is not yet xx.
SPOF: Single point of failure.
ASAP: As soon as possible.
BTW: By the way. By the way.
FYI: For your information. For your reference.
TTYL: Talk to you later.
Plz: Please homonym.
Thx: Thanks. Thanks.
AFAIK: As far as I know.
U: you.
R: are. Often used where R U? Not much is used in emails, most are used in informal occasions.
Wanna: want to. This is a convention, which means what you want to do.
Pvt: private. It is often used to express ownership, such as private libraries, or private code.
Doc: Document. If it is used in other occasions, it may also represent a doctor. So it needs to be combined with the context to judge.
ie that is ... (id est).
eg for example.
etc. et cetera, etc.
Repository: Referred to as Repo, which can be understood as "warehouse".
Issues: Can be understood as "issues", to give a simple example, if we open source a project, if someone has seen our project, and found a bug, or feel that there is room for improvement, he can give us Issue, etc. After we resolve the issue, we can close these issues; on the contrary, we can also propose the issue to others.
Star: It can be understood as "like". When we feel that a certain project has been done well, we can like this project, and the projects we have liked will be saved in our Star, which is convenient for us at any time. Check. In GitHub, if the number of points in a project can exceed 100, then this project is already very good.
Fork: It can be understood as a "pull branch". If we are interested in a certain project and want to develop new functions on this basis, then we can fork this project, which means copying one to complete the same project to In our GitHub account, it is independent of the original project. After that, we can develop in the project we copied.
Merge: It can be understood as a "merge". If someone forks our project, modifies it, and submits a pull request, then we can review the pull request. If the content of the pull request meets our requirements Requirements, and there is no conflict with our original project, we can merge it into our project. Of course, whether to merge is up to us.
Watch: It can be understood as "observation". If we watch an item, if there are any updates to this item, we will receive the update notification of the item at the first time.
Gist: If we do n’t have a project to open source or just want to share some code snippets, we can choose Gist.
