search

release-drafter / release-drafter

Drafts your next release notes as pull requests are merged into master.
https://github.com/marketplace/actions/release-drafter
ISC License
3.35k stars 326 forks source link

Configuration file is not found #1324

Closed justinmchase closed 1 year ago

justinmchase commented 1 year ago

Invalid config file { name: 'event', id: '4318991515', stack: 'Error: Configuration file .github/release-drafter.yml is not found. The configuration file must reside in your default branch.

I have the file in the .github/.github/release-drafter.yml at the org level but not in the individual repos (they all have the same settings), so why is it failing? Why should it need the file in the repo if there is a totally valid one at the org level?

Release Drafter also supports Probot Config, if you want to store your configuration files in a central repository. This allows you to share configurations between projects, and create a organization-wide configuration file by creating a repository named .github with the file .github/release-drafter.yml.

So does it also need an empty one in each repo or something? Why am I seeing this error?

image

justinmchase commented 1 year ago

The file is definitely there at the org level, yet it still can't find it.

Screen Shot 2023-03-02 at 9 52 56 PM

Screen Shot 2023-03-02 at 10 06 21 PM

jetersen commented 1 year ago

Since your taking screenshots I assume your .github repo is not public. So you need to you have two options make the .github public which is actually required for other features of the .github repo to work.

Or provide a PAT to resolve access between repos.

justinmchase commented 1 year ago

Yes its enterprise and its set to internal, but not private.

Do you think that this would be sufficient rather than a PAT? Which I don't think I'm going to be able to make easily for all the repos in the org.

        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
justinmchase commented 1 year ago

Actually I see I have already configured it this way and it doesn't work. What a huge bummer.

justinmchase commented 1 year ago

Seems to be related to this thread: https://github.com/actions/setup-node/issues/49

I'll close this for now since that seems to be the answer.

JoshuaTheMiller commented 1 year ago

❗ Please note I was wrong about the following- only Action resources are available 🤦‍♂️ I blame not having coffee yet this morning.

In case this proves helpful for others- at least within GitHub Enterprise (server/cloud), you can allow Actions from other repositories to read a specific repository. This can be done by performing the following steps:

  1. Go to the repository that you want a GitHub Action to read
  2. Go to Settings --> Actions --> General
  3. Select the proper Access setting based on your needs

image