Skip to content

ci: use different tokens to update docs and go version #52

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
zimeg merged 6 commits into from
Apr 21, 2025
Merged

ci: use different tokens to update docs and go version #52

Show file tree
Hide file tree
Changes from 2 commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
deebd92
ci: use different tokens to update docs and go version
zimeg Apr 18, 2025
4d934ca
docs: remove extra spaces from the authorizing page to test the workflow
zimeg Apr 18, 2025
ff58b63
docs: include notes on different required application permissions
zimeg Apr 21, 2025
393e2c2
docs: include a note of the actual environment variables used
zimeg Apr 21, 2025
fd7520a
docs: make it more clear that the docs and releaser links are apps
zimeg Apr 21, 2025
82c355e
chore: merge w 'main'
zimeg Apr 21, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions .github/workflows/dependencies.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,8 +12,8 @@ jobs:
id: credentials
uses: actions/create-github-app-token@v2.0.2
with:
app-id: ${{ secrets.GH_APP_ID }}
private-key: ${{ secrets.GH_APP_PRIVATE_KEY }}
Comment on lines -15 to -16
Copy link
Member Author

@zimeg zimeg Apr 18, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These tokens were for the kind @slack-cli-releaser[bot] of #5.

If these changes are alright I plan to delete these secrets to avoid future confusions 🫡

app-id: ${{ secrets.GH_APP_ID_RELEASER }}
private-key: ${{ secrets.GH_APP_PRIVATE_KEY_RELEASER }}
- name: Checkout the repo
uses: actions/checkout@v4.2.2
with:
Expand Down
4 changes: 2 additions & 2 deletions .github/workflows/sync-docs-from-cli-repo.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,9 +23,9 @@ jobs:
id: ghtoken
uses: actions/create-github-app-token@v2.0.2
with:
app-id: ${{ secrets.GH_APP_ID }}
app-id: ${{ secrets.GH_APP_ID_DOCS }}
owner: slackapi
private-key: ${{ secrets.GH_APP_PRIVATE_KEY }}
private-key: ${{ secrets.GH_APP_PRIVATE_KEY_DOCS }}

- name: Checkout the tool repo (source)
uses: actions/checkout@v4.2.2
Expand Down
5 changes: 3 additions & 2 deletions docs/guides/authorizing-the-slack-cli.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -72,7 +72,7 @@ Setting up a CI/CD pipeline requires authorization using a service token. Servic

To get a service token, you'll use the `slack auth token` command to get a `slackauthticket`, which you'll copy and paste into your workspace to exchange for the service token. The service token will not be saved to your `credentials.json` file; instead, it is presented in the terminal for you to copy and paste for use in your CI/CD pipeline. Once copied, you'll use the `slack login --auth <your-service-token>` command to authorize your Slack CLI. Detailed instructions are below.

:::info
:::info

The service token will not conflict with your regular authentication token; you can continue using your regular authentication token within the Slack CLI while using the service token for your CI/CD pipeline.

Expand All @@ -86,7 +86,8 @@ This "Slack service account" will be identical to other user accounts, but servi

### Obtaining a service token {#obtain-token}

Run the following command to get a `slackauthticket`:
Run the following command to get a `slackauthticket`:

```
slack auth token
```
Expand Down
Loading