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]: Auto Commenting feature for PR Merged #91

Closed
Asymtode712 opened this issue May 19, 2024 · 3 comments · Fixed by #107
Closed

💡[FEATURE]: Auto Commenting feature for PR Merged #91

Asymtode712 opened this issue May 19, 2024 · 3 comments · Fixed by #107
Assignees
@Asymtode712
Labels
enhancement New feature or request gssoc level1

Comments

@Asymtode712
Copy link
Contributor

Is your feature request related to a problem? Please describe.
Yes, the feature request is related to a problem. When pull requests (PRs) are merged in a project, it is often important to provide consistent feedback or notifications to the contributors. Currently, this process can be manual and time-consuming, leading to inconsistent communication and delayed acknowledgments. This can frustrate both maintainers, who have to remember to comment, and contributors, who might feel their efforts are not promptly recognized.

Describe the solution you'd like
To enhance our communication and acknowledgment process, we're implementing an auto-commenting feature for specific events within our project repository. This feature will automatically generate comments under the following circumstances:
PR Merged: Upon the successful merging of a pull request (PR), an auto-comment will be added to the corresponding issue, indicating that the PR has been merged and expressing gratitude to the contributor for their valuable contribution.

What problem is this feature trying to solve?
This feature aims to solve the problem of inconsistent and delayed communication following the merging of PRs. By automating the commenting process, it ensures that contributors receive timely feedback and acknowledgments. It also reduces the administrative burden on maintainers, allowing them to focus more on code reviews and other critical tasks.

PR merged

@sujaltangde please assign me this issue under gssoc'24
@Asymtode712 Asymtode712 added the enhancement New feature or request label May 19, 2024
@sujaltangde
Copy link
Owner

@Asymtode712 , Okay go for it

@Asymtode712 Asymtode712 mentioned this issue May 21, 2024
Merged
9 tasks
@Asymtode712
Copy link
Contributor Author

@sujaltangde For proper working of this workflow follow the below given steps:

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.

@github-actions GitHub Actions
Copy link

Hello @Asymtode712! Your issue #91 has been closed. Thank you for your contribution!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Asymtode712 Asymtode712

Labels
enhancement New feature or request gssoc level1
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Create autocomment-pr-merge.yml Asymtode712/JobLane
2 participants
@sujaltangde @Asymtode712