Below is my yml file for github actions

name: Close issues related to a merged pull request from dev branches.

on:
  pull_request:
    branches:
      - dev

jobs:
  closeIssueOnPrMergeTrigger:

    runs-on: ubuntu-latest

    steps:
      - name: Closes issues related to a merged pull request.
        uses: ldez/[email protected]
        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

I am already try create a pull request with commit message "Fix #30 xxx" into dev branch ( not default branch ) and approve the merge.. but it still not able to close my #30 issue after merge success.

need some help.. thanks.

It seems that this need a GH token but I can't see what are the required tokens for this.

Sometimes a developer will put a full stop after the issue number, e.g.
e.g. mantidproject/mantid#37397
This syntax works for pull requests targeting the default branch, so it would be nice if it worked here too.

If the issue you want to close is greater than 32767, it will just attempt to close issue number 32767 (see here). This is a problem for us because our issue numbers are now >36000.

mjolnir:
2024/01/30 10:58:00 strconv.ParseInt: parsing "36727": value out of range
 version     : 
 commit      : 
 build date  : 2024-01-30_10:57:56AM
 go version  : go1.19.3
 go compiler : gc
 platform    : linux/amd64
[Fixes #36727   #36727 ]
2024/01/30 10:58:00 PR #36765: closes issue #32767, add milestones 
2024/01/30 10:58:01 PR #36765: issue #32767, add comment: Closed by #36765.

This can probably be easily fixed by changing the issue type to explicitly use int32.

so in my PRs i tend to use text like this:

# PR details

## What changes did you make? (Give an overview)

- closes #627 
- closes #611 

...

that renders to:

unfortunately, your solution only picks up the first "closes" and completely skips the second. Looking at your readme, I suppose it expects closes #627, #611 instead but that does render as structured as my version which is why I would not want to shift:

any chance you could enhance your solution to, well, search for ALL occurrences of the keywords?