Support Projects Beta?

[thequailman]

Hello, this is a really handy action, any chance it could work with the new Projects setup and I could set fields with it? Ideally I'd like to have it also default to the current iteration (if the field is an iteration type).

[imjohnbo]

Thanks @thequailman! Happy to review a PR to that effect or add it myself when I get a chance. See #63 for previous discussion.

[Jblew]

Hi! I've just created a PR #73 with this feature :)

[imjohnbo]

Hi @thequailman, this is available in release v3.4.0 – let us know what you think 🙏.

Ideally I'd like to have it also default to the current iteration (if the field is an iteration type).

Due to limitations in the current GraphQL API in this area, we weren't able to do this just yet. Please let me know if you see something different.

[thequailman]

Thank you @Jblew @imjohnbo for making this happen! Too bad about the iteration stuff but I can work around that with some kind of triage status. I'll try this out sometime this week and see if I can contribute some docs or examples.

[parmouraly]

Hello @imjohnbo and @thequailman
Thank you both for raising this and implementing!
I'm currently trying to use it with

   - name: Generate token
      id: generate_token
      uses: tibdex/github-app-token@v1
      with:
        app_id: ${{ secrets.APP_ID }}
        private_key: ${{ secrets.APP_PEM }}

    - name: issue-bot
      uses: imjohnbo/issue-bot@v3.4.0
      env:
        TOKEN: ${{ steps.generate_token.outputs.token }}
      with:
        labels: "a, b, c"
        project-v2-path: "orgs/hello/projects/1"
        title: "[recurring] Upgrade blahblah"
        body: "asdf"
        token: ${{ env.TOKEN }}

But getting

Error: Error encountered: HttpError: Resource not accessible by integration.

Can you see any issues with the above syntax?
I've also tried specifying

project-type: "organization"

but no luck.

Thanks again!

PS: I have other jobs/actions that successfully use that TOKEN for projectsV2

[imjohnbo]

Hi @parmouraly, the error you're getting suggests the GitHub App installation access token you're using to authenticate does not have the proper scopes, or maybe APP_ID and APP_PEM are set incorrectly. Could you check?

Please open a new issue in case of further problems. Thanks!

[parmouraly]

Thanks for the reply @imjohnbo
As I mentioned I'm using this token for another action and it works fine.
See attached image for current permissions

I might raise an issue

Edit: In case anyone else sees this, it turned out (as can be seen in the above screenshot) that you need issues:write in order to create issues :-)