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.

Sign up for GitHub

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

Jump to bottom

[FEATURE] Would be nice to have bot be able to move issues between repositories #311

Open
2 tasks done
Souvikns opened this issue Sep 9, 2024 · 5 comments · May be fixed by #314
Open
2 tasks done

[FEATURE] Would be nice to have bot be able to move issues between repositories #311

Souvikns opened this issue Sep 9, 2024 · 5 comments · May be fixed by #314
Labels
enhancement New feature or request

Comments

@Souvikns
Copy link
Member

Souvikns commented Sep 9, 2024

Why do we need this improvement?

To move a issue from one repo to another, you need to be codeowner to both the repositories that you are trying to move. Which is however not possible, so a bot command that does that would be awesome.

Issues like asyncapi/cli#1488 cannot be transfered because there is no common codeowner between CLI and modelina.

How will this change help?

Repositories that implement other AsyncAPI tools like CLI. When encounterd bug most of the time it has to do with something with the underlying library. So to be able to move the issue to the right repo, helps in solving the problem faster.

Screenshots

No response

How could it be implemented/designed?

A simple bot command like /rtm that accepts the repo name to move as a input. Something like /mv modelina. Would be nice if only code owner of the repo could run this command.

🚧 Breaking changes

No

👀 Have you checked for similar open issues?

  • I checked and didn't find a similar issue

🏢 Have you read the Contributing Guidelines?

Are you willing to work on this issue?

Yes I am willing to submit a PR!
@Souvikns Souvikns added the enhancement New feature or request label Sep 9, 2024
@derberg
Copy link
Member

derberg commented Sep 9, 2024

best would be to reflect the the name of the feature in the command name so /transfer-issue and /ti

@derberg
Copy link
Member

derberg commented Sep 9, 2024

here are examples how workflow for commands in issues look like:

so yeah, add new workflow file, with suffix command and use actions/github-script as above examples

also this help command needs to be updated

@asyncapi-bot
Copy link

Hello, @derberg! 👋🏼

I'm 🧞🧞🧞 Genie 🧞🧞🧞 from the magic lamp. Looks like somebody needs a hand!

At the moment the following comments are supported in issues:

  • /good-first-issue {js | ts | java | go | docs | design | ci-cd} or /gfi {js | ts | java | go | docs | design | ci-cd} - label an issue as a good first issue.
    example: /gfi js or /good-first-issue ci-cd

@derberg
Copy link
Member

derberg commented Sep 9, 2024

and yeah, as you can see above, switch approach to startsWith instead of contains in case of your command, as contains causes that bot pick up for example help command if it is just part of the URL in the comment as in my last comment

@Souvikns
Copy link
Member Author

Souvikns commented Sep 10, 2024 •
edited
Loading

I couldn't find any REST API endpoint that transfers issues, but gh cli can do that https://cli.github.com/manual/gh_issue_transfer and also a graphql mutation that can do this https://docs.github.com/en/graphql/reference/mutations#transferissue

@Souvikns Souvikns linked a pull request Sep 11, 2024 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

ci: add command for transferring issue Souvikns/.github
3 participants
@derberg @Souvikns @asyncapi-bot