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

ci: add command for transferring issue #314

Open
wants to merge 16 commits into
base: master
Choose a base branch
from

Conversation

Souvikns
Copy link
Member

Description
In this PR I am adding a new workflow file to trasfer issue from one respository to another in AsyncAPI organisation. The command is /trasfer-issue {repo-name} or /ti {repo-name} for example

/trasfer-issue cli
/ti bundler

Related issue(s)

Resolves #311

Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Welcome to AsyncAPI. Thanks a lot for creating your first pull request. Please check out our contributors guide useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.

@derberg derberg changed the title feat: add command for transferring issue. ci: add command for transferring issue Sep 16, 2024
Copy link
Member

@derberg derberg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

left some comments,

you also need to add this new workflow to https://github.com/asyncapi/.github/blob/master/.github/workflows/global-replicator.yml#L141 to have it replicated to all other repos


jobs:
transfer:
if: ${{(!github.event.issue.pull_request && github.event.issue.state != 'closed' && github.actor != 'asyncapi-bot') && (contains(github.event.comment.body, '/trasfer-issue') || contains(github.event.comment.body, '/ti'))}}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we should probably start using starts with instead of contains

@KhudaDad414 thoughts?

@Souvikns Souvikns requested a review from derberg September 23, 2024 05:51
@derberg
Copy link
Member

derberg commented Dec 18, 2024

@Souvikns ping in case you forgot about this one

@Souvikns
Copy link
Member Author

I have tested the action here: https://github.com/Klifu/API/actions/runs/12532481994.
You can play around with the functionalities using this repo: https://github.com/Klifu/API, for now only CLI repo has issues so you can transfer issues to there.

@Souvikns
Copy link
Member Author

@derberg I made the changes, now fetching repo from github context and added missing env for REPO_TO_MOVE.

@derberg
Copy link
Member

derberg commented Jan 29, 2025

code wise lgtm, did you test it in some repo? just to be 100% sure? as once I merge this one, it will be pushed to all repos.

maybe you can add it first to CLI manually, with the same file name (so it will be later overwritten by this PR))

@derberg
Copy link
Member

derberg commented Jan 29, 2025

I'm only referring to transfer-issue.yml file

also please add the same header comment as other workflows here have

@derberg
Copy link
Member

derberg commented Feb 11, 2025

@Souvikns you need help?

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

Successfully merging this pull request may close these issues.

[FEATURE] Would be nice to have bot be able to move issues between repositories
2 participants