-
-
Notifications
You must be signed in to change notification settings - Fork 4
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
Default the repository value? #15
Comments
Good call! Thanks. @JisanAR03 can you make that change please? |
@DonnieBLT yeah sir sure |
@DonnieBLT sir , we can close this issue |
@JisanAR03 For future reference you can close issues from pull requests on merge using keywords: https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/using-keywords-in-issues-and-pull-requests#linking-a-pull-request-to-an-issue |
@kingthorin sir , Thanks for the docs sir, I will something about it for sure☺ |
@DonnieBLT sir , to close an issue automatically, as @kingthorin sir says, I come with a solution.
It's just an approach, sir. Any suggestions for me to implement auto-issue close action? |
Oh I was just pointing it out for the next time you worked on an issue so that you didn't have to ask someone to close things. I didn't mean for it to be something you had to integrate. (If you can and want to then cool, but that wasn't the point 🙂) |
Also, if you use GitHub to create the branch from the issue, it will automatically link it to the information section on the right. |
@kingthorin , sorry for my misunderstanding, sir😬 |
No worries. Looking back I wasn't very clear. |
For my 2 cents this issue has been addressed, I'm happy to close it if you want. Just let me know @JisanAR03 |
@kingthorin yes sir sure |
Won't this almost always be the necessary value?
Why not simply default it and allow users to override instead of requiring it to be set as a
with
value?The text was updated successfully, but these errors were encountered: