I had the privilege to create PR #1337 at work this week

It's software development lingo, sorry for that.

When a software development team works on a project made of files containing code, each member can work independently on its own copy (called a "branch") of the "main" version of the code. Once a developer is happy of his modifications, he submits his changes to the team for review, before the changes can be merged to the "main" version.
This presentation of the modifications and review process is sometimes called a "merge request" or a "pull request". "Pull", because historically, other members would pull the version to their own machine for analysis. Nowadays, it can all be done on a web page (on GitHub for example). The PR has a tab for the modifications description and discussion, and a tab that highlights all the differences in the code between the "main" version and the new modified version.

When one creates such PR, a sequential number is automatically attributed, it serves as a quick identifier for the PR. And I was lucky to be the one to open the 1337th PR on this project. It's quite insignificant, just a little coolness factor.

7 comments

Haha, rad :D
Got curious and checked our system and sadly the id does not even exist. Probably too long ago from when we used another system 🤔
Nice
What is PR #insertNumber?
- Pull request. Basically to make some code changes and are asking for them to be accepted
- It's software development lingo, sorry for that.
  When a software development team works on a project made of files containing code, each member can work independently on its own copy (called a "branch") of the "main" version of the code. Once a developer is happy of his modifications, he submits his changes to the team for review, before the changes can be merged to the "main" version.
  This presentation of the modifications and review process is sometimes called a "merge request" or a "pull request". "Pull", because historically, other members would pull the version to their own machine for analysis. Nowadays, it can all be done on a web page (on GitHub for example). The PR has a tab for the modifications description and discussion, and a tab that highlights all the differences in the code between the "main" version and the new modified version.
  When one creates such PR, a sequential number is automatically attributed, it serves as a quick identifier for the PR. And I was lucky to be the one to open the 1337th PR on this project. It's quite insignificant, just a little coolness factor.
  
  Oh that’s pretty cool! The number and the system. Never really used github, branches or anything like that. My tiny software projects were never big enough to warrant heavy infrastructure like that, so I never looked into it.