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

Support .github repo label.yml file #3

Open
jetersen opened this issue Oct 21, 2019 · 3 comments · May be fixed by #125
Open

Support .github repo label.yml file #3

jetersen opened this issue Oct 21, 2019 · 3 comments · May be fixed by #125
Assignees

Comments

@jetersen
Copy link

Would be great to support the .github repo style of deep merging the label.yml

So you could have default labels from organization. 👍

@crazy-max
Copy link
Owner

Hi @Casz, thanks for your suggestion!

I had thought about integrating this feature but for the moment the scope of a GITHUB_TOKEN is not expanded to the org (yet?). The only way would be to use a GitHub PAT.

Considering this I think we should modify the YAML config to something like:

repos:
  - "." # means current repo
  - "myorgname/*"
  - "myusername/*"
  - "myusername/arepo"
labels:
  - name: mylabel
    color: "000000"
  - ...

@jetersen
Copy link
Author

jetersen commented Oct 21, 2019

I could perhaps provide my own GitHub token that has the necessary access ? 😄

@jetersen
Copy link
Author

By definition the .github repo has to be public at least according to GitHub docs that would mean the default token should suffice.

https://docs.github.com/en/free-pro-team@latest/github/building-a-strong-community/creating-a-default-community-health-file#creating-a-repository-for-default-files

You can add default community health files to the root of a public repository called .github that is owned by an organization or user account.

Make sure the repository status is set to Public (a repository for default files cannot be private).

@jetersen jetersen linked a pull request Jan 8, 2021 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants