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

[Feat]: Workflow for closing issues on merging PR linked to that issue #28

Closed
Asymtode712 opened this issue May 21, 2024 · 6 comments · Fixed by #29
Closed

[Feat]: Workflow for closing issues on merging PR linked to that issue #28

Asymtode712 opened this issue May 21, 2024 · 6 comments · Fixed by #29
Assignees
Labels

Comments

@Asymtode712
Copy link
Contributor

Describe the feature

As the repo maintainers have to manually close an issue after merging a PR linked with that issue, I propose a workflow where the issue linked with a PR which be automatically closed when that PR is merged by the maintainer and efforts will be saved.

Copy link

Thank you for creating this issue! 🎉 We'll look into it as soon as possible. In the meantime, please make sure to provide all the necessary details and context. If you have any questions or additional information, feel free to add them here. Your contributions are highly appreciated! 😊

You can also check our CONTRIBUTING.md for guidelines on contributing to this project.

@Asymtode712
Copy link
Contributor Author

@MAVRICK-1 please assign me this issue under gssoc'24

@MAVRICK-1
Copy link
Owner

@Asymtode712 go ahead

@Asymtode712
Copy link
Contributor Author

@MAVRICK-1 Please carry out the steps given below so that this and other workflows can run properly:

Step 1: Create a Personal Access Token (PAT) with repo Permission

1. Navigate to Settings:

  • Click on your profile picture in the upper-right corner of the page.
  • Select "Settings" from the dropdown menu.

2. Go to Developer Settings:

  • In the left sidebar, scroll down and click on "Developer settings."

3. Create a New Token:

  • Click on "Personal access tokens" in the left sidebar.
  • Click on the "Generate new token" button.

4. Configure the Token:

  • Token Description: Enter a descriptive name for the token (e.g., Repo Access Token).
  • Expiration: Set no expiration.
  • Select Scopes: Check the box next to repo to grant full control of private repositories.

5. Generate Token:

  • Scroll down and click on the "Generate token" button.
  • Important: Copy the token to a secure location. You will not be able to see it again once you navigate away from the page.

Step 2: Assign the Token to GITHUB_TOKEN Environment Variable

1. Navigate to Your Repository:

  • Go to your repository on GitHub.
  • Click on the "Settings" tab.

2. Go to Secrets:

  • In the left sidebar, click on "Secrets and variables" and then "Actions".

3. Create a New Secret:

  • Click on the "New repository secret" button.
  • Name: Enter GITHUB_TOKEN.
  • Value: Paste your generated token.
  • Click on the "Add secret" button.

@MAVRICK-1
Copy link
Owner

change the name of the variable to SECRET_GITHUB_TOKEN

@Asymtode712
Copy link
Contributor Author

ok

MAVRICK-1 added a commit that referenced this issue May 22, 2024
added the workflow as mentioned in #28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants