Some technical school -github common usage and abbreviations

  • PR:. Pull Request a pull request, submit code to other projects
  • LGTM:. Looks Good To Me looks good, code is review, can be combined
  • SGTM: Sounds Good To Me and the above phrase meaning almost.
  • WIP: Work In Progress change if you have a great PR, may be submitted in written part of the case, wrote in the title on WIP, to tell the maintainer of this feature has not been completed, convenient defenders advance review section. code is submitted.
  • PTAL: Please Take A Look you to Chou Chou.? Others look for tips
  • TBR:. To Be Reviewed prompt defenders review
  • TL; DR:. Too Long; Did not Read too long, did not see.
  • TBD:. To Be Done (or Defined / Discussed / Decided / Determined) differ depending on the significance of context, but are generally not xx.
  • Repository: Short Repo, it can be understood as "warehouse"
  • Issues: can be understood as "problem", cite a simple example, if we open a project, if other people saw our project, and found a bug, or feel that to be desired, he can propose to us Issue, etc. Issues after we solve, you can put these Issues closed; on the contrary, we can also propose Issue to others.

  • Star: can be understood as "thumbs up" when we feel a particular project to do better, you can think that this project thumbs up, thumbs up and we have the item, we will be saved to the Star, to help us at any time View. Among GitHub, if the point number of stars a project capable of over one hundred, then the description of this project has been very good.

  • Fork: can be understood as "pull branch," if we are more interested in a particular project, and you want this basis to develop new features, then we can Fork this project, which represents a complete copy of the same project to among our GitHub account, and it is independent of the original project. After that, we can develop a project in its own replication.

  •  

    Merge: can be understood as a "merger", if someone Fork of our project, it was revised and presented Pull request, then we can on the Pull request for review. If the Pull requested content to meet our requirements, and with our original project there is no conflict, then it can be merged into our project. Of course, whether the merger, decided by us.

  •  

    Watch: can be understood as "observation", if we Watch a project, and then, if the project had any updates, we will receive an update notification of the project in the first time.

  •  

    Gist: If we can not have an open source project or just simply want to share snippets of code, we can choose Gist.

  • AFAIK: As far as I know to my knowledge.
  • SPOF: Single point of failure. Single node crashes
  • ASAP: As soon as possible. Immediately, as soon as possible.
  • BTW: By the way. By the way
  • FYI: For your information. for your reference
  • TTYL: Talk to you later. Will be back to you
  • Plz: Please homonym
  • Thx: Thanks Thank you.
  • U: you
  • R: are often used where RU.? Mail which is not much use, most used in an informal setting.
  • Wanna: want to. This belongs to the convention, he represents want to do.
  • Pvt:. Private ownership is often used to represent the above, for example, a private library, or proprietary code.
  • Doc:. Document If used in other cases, it could mean a doctor. It is necessary to determine in context
  • ie is ...  (the above mentioned id est)
  • eg e.g. for example, 
  • etc. etc. et cetera

Guess you like

Origin www.cnblogs.com/peixuewen/p/11563475.html