Skip to content

Commit d3cbc44

Browse files
zimegmwbrooks
andauthored
ci: update upstream documentation if the event referenced on the main branch (#55)
Co-authored-by: Michael Brooks <[email protected]>
1 parent dbebe74 commit d3cbc44

File tree

2 files changed

+4
-4
lines changed

2 files changed

+4
-4
lines changed

.github/workflows/sync-docs-from-cli-repo.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -53,7 +53,7 @@ jobs:
5353
npm run build
5454
5555
- name: Create a pull request
56-
if: ${{ github.event.pull_request.merged || github.event_name == 'workflow_dispatch' }}
56+
if: ${{ github.ref_name == github.event.repository.default_branch || github.event_name == 'workflow_dispatch' }}
5757
id: site-pr
5858
uses: peter-evans/[email protected]
5959
with:

docs/guides/deploying-with-the-slack-cli-and-github-actions.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ Once created, copy the link and share it in a Slack channel. You'll see a button
2929

3030
## Obtain a service token {#obtain-service-token}
3131

32-
To automate subsequent deployments, we'll need to obtain a [service token](/slack-cli/guides/authorizing-the-slack-cli#ci-cd) for the app.
32+
To automate subsequent deployments, we'll need to obtain a [service token](/slack-cli/guides/authorizing-the-slack-cli#ci-cd) for the app.
3333

3434
Navigate to the root directory of your project and run the `slack auth token` command. You'll be prompted to run a slash command called `slackauthticket`, similar to the way you authorized your app earlier. Copy that command and run it in Slack, then copy the challenge code you receive and enter it into your terminal. You'll see a service token that starts with `xoxp-` &mdash; make sure you save this token. Note that this token is connected to a specific workspace and organization.
3535

@@ -78,7 +78,7 @@ jobs:
7878
slack deploy -s --token $SLACK_SERVICE_TOKEN
7979
```
8080
81-
This file instructs the Slack CLI to deploy the latest revision of your repository to the Slack platform when any changes are pushed to the main branch.
81+
This file instructs the Slack CLI to deploy the latest revision of your repository to the Slack platform when any changes are pushed to the main branch.
8282
8383
You can go with any other Linux option you prefer for the GitHub-hosted runner; refer to [About GitHub-hosted runners](https://docs.github.com/en/actions/using-github-hosted-runners/about-github-hosted-runners/about-github-hosted-runners#viewing-available-runners-for-a-repository) for more details.
8484
@@ -90,7 +90,7 @@ Your GitHub repository is now set up for team collaboration! Your team members c
9090
9191
## Further reading {#read}
9292
93-
Check out these articles to expand your knowledge and skills of automated deployments and the Slack CLI:
93+
Check out these articles to expand your knowledge and skills of automated deployments and the Slack CLI:
9494
9595
➡️ [CI/CD overview and setup](https://tools.slack.dev/slack-cli/guides/setting-up-ci-cd-with-the-slack-cli)
9696

0 commit comments

Comments
 (0)