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

This might be caused by a malformed issue title, or a typo in the labels or assignees. #73

Closed
1UC1F3R616 opened this issue Nov 21, 2020 · 4 comments

Comments

@1UC1F3R616
Copy link

  • I am getting below error and I have tried many changes in the template file, used default one but getting this error every time.

image

  • It also says bad credentials, can it be because of token that I am using is missing some required permissions?

  • Example Issue template that I used:

---
title: Someone just pushed
assignees: 1uc1f3r616
labels: bug
---
Someone just pushed, oh no! Here's who did it: {{ payload.sender.login }}.
  • Actions template
on: [pull_request]
name: dependabot bot issue
jobs:
  stuff:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v2
      - uses: JasonEtco/create-an-issue@v2
        env:
          GITHUB_TOKEN: ${{ secrets.MY_GITHUB_TOKEN }}
        with:
          filename: .github/dependabot.md
@1UC1F3R616
Copy link
Author

1UC1F3R616 commented Nov 21, 2020

I created my own GitHub Token but now I thought that this might be server-side secret and has to be what you have put in the examples ie. GITHUB_TOKEN only. So I changed it and now error is slightly different
image

It's giving Resource not accessible by integration error now

@JasonEtco
Copy link
Owner

👋 It's a little unclear, but the GitHub API sometimes returns this if the token doesn't have enough access to:

  • Know that that user exists
  • Can be assigned to the issue

If the built-in secrets.GITHUB_TOKEN works for your use-case, you should use that.

@chenqhxyz
Copy link

Hi,

I faced the same issue when I tried to use my other account to open an issue on repository owned by this account.

I think one of the reasons is because the secrets.GITHUB_TOKEN my other account has doesn't have enough permission to create an issue in the repo belong to current account, right? Any idea to solve this?

Thanks.

@JasonEtco
Copy link
Owner

(Realizing it's way too late to be helpful, but): Actions' GITHUB_TOKEN is scoped to the repository it's running in. You can use a personal access token to make requests to a different repository.

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

3 participants