3b092b4cb8
* Update enterprise-server-releases.js * Run deprecation script * Remove finding / managing security vulnerabilities * remove vuln from translations * remove more dead pages * Restore heavily used files * Remove 2.22 refs in tests * Update working-with-the-npm-registry.md
46 lines
1.4 KiB
Markdown
46 lines
1.4 KiB
Markdown
You can specify an environment for each job in your workflow. To do so, add a `jobs.<job_id>.environment` key followed by the name of the environment.
|
|
|
|
For example, this workflow will use an environment called `production`.
|
|
|
|
```yaml
|
|
name: Deployment
|
|
|
|
on:
|
|
push:
|
|
branches:
|
|
- main
|
|
|
|
jobs:
|
|
deployment:
|
|
runs-on: ubuntu-latest
|
|
environment: production
|
|
steps:
|
|
- name: deploy
|
|
# ...deployment-specific steps
|
|
```
|
|
|
|
When the above workflow runs, the `deployment` job will be subject to any rules configured for the `production` environment. For example, if the environment requires reviewers, the job will pause until one of the reviewers approves the job.
|
|
|
|
You can also specify a URL for the environment. The specified URL will appear on the deployments page for the repository (accessed by clicking **Environments** on the home page of your repository) and in the visualization graph for the workflow run. If a pull request triggered the workflow, the URL is also displayed as a **View deployment** button in the pull request timeline.
|
|
|
|
```yaml
|
|
name: Deployment
|
|
|
|
on:
|
|
push:
|
|
branches:
|
|
- main
|
|
|
|
jobs:
|
|
deployment:
|
|
runs-on: ubuntu-latest
|
|
environment:
|
|
name: production
|
|
url: https://github.com
|
|
steps:
|
|
- name: deploy
|
|
# ...deployment-specific steps
|
|
```
|
|
|
|
|