We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
path must not be empty
hi thanks for your great work on this action. Could you please provide some help on an error I ran into?
I'm using yml file like this:
name: Auto Label on: pull_request: branches: - 'release-*' types: [opened] jobs: auto-label: name: Auto Label runs-on: ubuntu-latest steps: - uses: actions/checkout@v2 - uses: banyan/[email protected] env: GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
and get path must not be empty error.
My error log is:
Run banyan/[email protected] with: configPath: .github/auto-label.json env: GITHUB_TOKEN: *** ##[error]path must not be empty
My json file is:
{ "rules": { "status/PTAL": [".md", ".yml", ".yaml", ".json", "media/", "scripts/"] } }
My PR link: pingcap/docs-cn#3631. Any clue on this? @banyan
The text was updated successfully, but these errors were encountered:
I also had this issue. Did you discover the cause of this, @yikeke?
Sorry, something went wrong.
This happens to us when pull request are opened from forks.
same here, Run banyan/[email protected] with: configPath: .github/auto-label.json env: GITHUB_TOKEN: *** Error: path must not be empty
only when PR from forks. the forks contains the file .github/auto-label.json , I wish I could see what the "path" is that is supposedly empty
No branches or pull requests
hi thanks for your great work on this action. Could you please provide some help on an error I ran into?
I'm using yml file like this:
and get
path must not be empty
error.My error log is:
My json file is:
{
"rules": {
"status/PTAL": [".md", ".yml", ".yaml", ".json", "media/", "scripts/"]
}
}
My PR link: pingcap/docs-cn#3631. Any clue on this? @banyan
The text was updated successfully, but these errors were encountered: