Update: As of March 21, 2024,
https://jobs.github.com/has been sunset.Today we are announcing the deprecation of GitHub Jobs and, on August 19th, will sunset the site entirely. Over the past year, we've seen that most of the positions listed on GitHub Jobs are already posted elsewhere, and most developers who use GitHub are looking elsewhere. To best serve the GitHub developer community, we will be sunsetting the site.
The deprecation and shutdown of GitHub Jobs will follow this timeline:
- April 19, 2021: Every page on GitHub Jobs will display a banner indicating the deprecation and shutdown dates and linking to this post.
- May 19, 2021: New job postings will no longer be accepted by GitHub Jobs.
- June 9-10, June 29 – July 1, July 20-22, August 2-6: The JSON and Atom APIs will brownout so they will return only an error message indicating the deprecation and shutdown dates and linking to this post.
- August 19, 2021:
https://jobs.github.com/will redirect to this blog post.- March 21, 2024:
https://jobs.github.com/has been sunset.
Sunsetting API Authentication via Query Parameters, and the OAuth Applications API
In February 2020, to strengthen the security of our API, we deprecated API Authentication via Query Parameters and the OAuth Application API to avoid unintentional logging of in-transit access tokens. In the coming months, we'll be removing these endpoints and authentication flow according to the following schedule:
OAuth Application API
Please refer to this blog post on migrating to the replacement endpoints.
Brownouts
- May 5, 2021: For 12 hours starting at 14:00 UTC
- June 9, 2021: For 24 hours starting at 14:00 UTC
Removal
- August 11 2021 at 14:00 UTC
Authentication via Query Parameters
Please refer to this blog post for authentication via headers.
Brownouts
- May 5, 2021: For 12 hours starting at 14:00 UTC
- June 9, 2021: For 24 hours starting at 14:00 UTC
- August 11, 2021: For 48 hours starting at 14:00 UTC
Removal
- September 8 2021 at 14:00 UTC
Please check the latest Enterprise release notes to learn in which version these functionalities will be removed.
GitHub Actions now supports a concurrency key at both the workflow and job level that will ensure that only a single run or job is in progress.
There are a number of scenarios where you only want a single instance of a particular workflow or job running at any given time. For example: if you have a deployment to your production environment ensuring that only a single deployment is happening at any given time and that you are always deploying the latest code can be important. The concurrency key can be any string or an expression using the github context. When a job or run starts it first checks to see if anything is currently holding on to the concurrency group specified. If not, it will start. If there is a lock on the group, the job or run will be marked as pending and will only start after the blocking job or run completes.
Learn more about concurrency groups in GitHub Actions