Skip to content
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.

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

Automate little dev tasks and make them consistent. #10

Open
thorwhalen opened this issue Apr 5, 2021 · 1 comment
Open

Automate little dev tasks and make them consistent. #10

thorwhalen opened this issue Apr 5, 2021 · 1 comment
Assignees

Comments

@thorwhalen
Copy link
Member

I'll take one as an example.

For a given repository, I could specify a default label that would be used for any new issues I create. Though it's a small overhead, it's just one of those "one more thing to click" that can become annoying. (posted on statckoverflow)

I've tried that answer, but it failed for me (said I didn't provide a github_token (though I see it in secrets).

Note: Apparently, you can't use GITHUB_TOKEN as an environment name (see https://github.ghproxy.topmunity/t/all-github-actions-suddenly-failing-with-github-token-secret-does-not-exist/16108). I used GH_TOKEN

My .workflows/main.yml is:


name: Add Label

on:
  issues:
    types: [opened]

jobs:
  add_label:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v2
      - uses: actions-ecosystem/action-add-labels@v1
        with:
          github_token: ${{ secrets.GH_TOKEN }}
          labels: enhancement
@thorwhalen
Copy link
Member Author

Another example would be having particular repositories have an default assignee (for example, this isee one would be Valentin) if none is given.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants