Node.js 12 actions are deprecated. For more information see: https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/. Please update the following actions to use Node.js 16: 755f9b6

test workflow

It would be nice to reference built-in templates for common software lifecycle tasks, e.g. the ones that you can add from the Settings UI:

But this functionality doesn't belong in issue-bot. Explore if 3rd party actions exist, if imjohnbo/extract-issue-template-fields should be renamed or extended, or if a new action should be created.

Summary

Accept pinned: true as an input to pin the weekly radar issue (docs, v4 API).

It would be a nice feature if we could assign the new issue to a Project and Milestone by name. A good API may be if the user could specify two new inputs:

project
milestone

Hi,

I m trying to figure out the project and also made a template on my sample project. As I see, the issue-bot creating the issue but
I want to set the issue creator as me :) . Is this possible ?
Thanks

Problem

GitHub App installation access tokens are a valid way to authenticate with Issue Bot, but it's undocumented.

Solution

Let's document it in docs/example-workflows!

I think the previous-issue-number idea is great!!
Being able to specify where it can be overwritten solves my problem.

I'd love to see it happen!

Originally posted by @soudai in #31 (comment)

Just as before with Node 12, Node 16 Actions are deprecated: #80

This is a very useful Action and it would be great to see it bumped up to Node 20 to stay current 🙏

v3.0.0 added the ability to add issues to repository project boards. It'd be nice to also be able to add issues to organization project boards.

Hello,

Are projects working for everyone? I can't seem to make it work.

This is the error I get:

Unexpected input(s) 'project-type', valid inputs are ['title', 'body', 'labels', 'assignees', 'project', 'column', 'milestone', 'pinned', 'close-previous', 'linked-comments', 'rotate-assignees']

And here's my code:

name: Weekly
on:
  workflow_dispatch:
  schedule:
    - cron:  '20 07 * * 1'

jobs:
  create_issue:
    name: Send Newsletter
    runs-on: ubuntu-latest
    permissions:
      issues: write
    steps:
      - name: Send Newsletter
        uses: imjohnbo/[email protected]
        with:
          assignees: "john"
          labels: "workjohn"
          title: "Send Newsletter"
          body: |
                "You know what to do, Rico!"          
                
          project-type: "user"
          project: "2"  
          column : "This Week"
          pinned: false
          close-previous: false
        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

As you can see, I'm using the v3.0 of the bot, but I still can't get it to work. I'm on a user account and the Project I want to access is the one of my "user level" project (not the repository one).

Summary

Accept template: ./path/to/issue-template as an input to generate the issue based on a template instead of a hard coded string.

Items to include in v3:

• #16
• #22
• #28

Parameterize previous text:
https://github.com/imjohnbo/issue-bot/blob/main/lib/issue-bot.js#L182

and next text:
https://github.com/imjohnbo/issue-bot/blob/main/lib/issue-bot.js#L189

I want to use your Github action to create Issues for some tests after a deployment process. After each release I want to close the old issues.
If there is no issue yet (on the first release), I logically get the error: Couldn't find previous issue with labels.
Would it be possible not to throw an error if there is no issue with these labels yet?

Although the documentation recommends Github App, it will not work properly without DeviceFlow enabled.
I think we need to explicitly state this somewhere.

Related to #72.

https://stackoverflow.com/questions/75391023/is-it-possible-to-create-a-user-project-v2-with-a-github-app

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).

Hi thanks for the lib! I hope it can generate issues with dates in it. For example, create an issue everyday with name Today's meeting (2022.05.22) etc.

Add tests using jest and nock

If issue long time not response, how to close it use robot

The set-output command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

I use Issue Bot for creating daily checklists and features and I use the assign feature to notify myself that a new issue has been created and to fill it in etc.

Proposal

I'd love to see this feature implemented or considered using a value like: remove-assignees: true/false
With an option to select which assignees to automatically remove. Similar to the assignees: "user1, user2"

I've added a suggestion as to how this might look in the config.yml.

with:
        assignees: "octocat, monalisa"
        close-previous: true
        remove-closed-issue-assignees: true # whether to remove assignees from a close previous issue
        remove-assignees: "octocat"   # removes specific assignee
        remove-all-assignees: true # if true removes all assignees from an issue before closed

👋 I noticed that my scheduled issues failed this morning with:

/home/runner/work/_actions/imjohnbo/issue-bot/v2/dist/index.js

I was able to get them working by reverting to 2.4:

uses: imjohnbo/[email protected]

This is a test issue

I want to take over the previous Body when creating an issue on a regular basis.

For example, when taking over an unresolved task.

Proposal 1

If use_old_body: true is specified, it will be overwritten with the old Body.

I think you just need to implement it here.

But not convenient.

Proposal 2

Take over only a specific part.

For example.
take_over_word: "take over"

old issue

# tesk
- [x] aaa
- [x] bbb
- [ ] ccc

#  take over
- [x] hoge
- [x] fuga
- [ ] foo
- [ ] bar

new issue

# tesk
- [ ] aaa
- [ ] bbb
- [ ] ccc

#  take over
- [x] hoge
- [x] fuga
- [ ] foo
- [ ] bar

Template overwrites task.
The location of the specified keyword remains the same.

This is good, but unfortunately I didn't seem to be able to implement it right away.

I used a hr, line break (------ in markdown) in my template, and the new issue generated was split and only posted what was above that line break.

My hunch is this is related to the template parser, something like this code?

Thanks for the great action!

In one of my workflows, I have a step looking like that:

      - name: Run tests
        run: ...

      - name: Open issue
        if: failure()
        uses: imjohnbo/issue-bot@v2
        with:
          title: CI Failure
          labels: bug, ci
          pinned: true
          close-previous: true
          template: .github/templates/ci-failure.md

When tests are failing, then issue-bot creates an issue. However, it also closes the last issue with a bug label. Not with a bug AND ci label. Only with a bug label.

I would expect issue-bot to close the last created issue with these two labels.

Hi folks

I can successfully make issues with this github action; however I can't successfully add them to projects. I have a Github App with the right permissions; but keep seeing errors like:

GraphqlError: Could not resolve to a ProjectV2 with the number 4

or

HttpError: Resource not accessible by integration.

Suggestions?

You can see here a goal and a method.
To make it easier to use this method, I'd let GitHub convert a new task to an issue and open a task list. (Otherwise, one has to press the corresponding buttons.)
I'm trying to find out whether this is possible. It might be possible:
a. with this action or another from the GitHub marketplace
b. with an action created by me
c. with a feature created by the GitHub team
What can you and I do to achieve at least this simplification, if not the main goal?

Hi,

I've got something like

- name: issue-bot
      uses: imjohnbo/[email protected]
      env:
        TOKEN: ${{ steps.generate_token.outputs.token }}
      with:
        labels: "maintenance, recurring, patching"
        project-type: "organization"
        project-v2-path: orgs/hello/projects/1
        column: "To Do"
        pinned: false
        close-previous: false
        linked-comments: false
        title: "[recurring] Upgrade to most recent image"
        body: ${{ steps.extract.outputs.body }}
        token: ${{ env.TOKEN }}

The new issue makes it into the project but not into the correct column.

Are you able to confirm this? If so do you think a fix would be possible?

Hi, is it possible to mirror any created issues on a public repository to a private repo?
[public issues but private code]

Said issues also need to close when closed on the private repo.

A suggestion: I only wan't to open an issue, if there is not already an issue with the same title. I'm aware of the close-previous functionality, but i want to preserve history on an existing issue. My usecase is output from trivy.

Hi,

In our GH action we have a step to automatically add certain issues to one of our GH projects.
See sample config bellow:

- name: issue-bot
      uses: imjohnbo/issue-bot@v3
      with:
        labels: "a, b, c"
        project: 1
        column: "To do"
        pinned: false
        close-previous: false
        linked-comments: false
        title: "[recurring] Example task title"
        body: ${{ steps.extract.outputs.body }}
      env:
        GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

This has been working fine but up to 8 days ago.

I noticed this change was released 11 days ago and I think it's related to the runtime error we get, which I believe for us is occurring here