-
-
Notifications
You must be signed in to change notification settings - Fork 148
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
improve readme #1087
Comments
This is not a bug and you did not even bother to describe your reasoning |
it's just a blank issue to link a PR, no need to read it, it's self close when PR it's valided |
coudl you merge my pr before close this issue please ?, it's only to link for release update |
No, I am not going to merge your PR |
why ? i just improve the readme |
Issues on GitHub are meant to categorize and discuss bugs and new features. Minor changes like updates to README or If you wish, you can just your Pull requests to issues on your private fork of AntiMicroX, but there is no need to create an independent issue dedicated to minor change in README |
I was taught to always link a pr to an exit to make it easier to follow, and I apply this rule, but okay. |
This is a good practise, but in case of implementing features or fixing bugs with existing reports. In situations like: minor fixes in docs, minor refactors or cleanups creating issue is not necessary. |
Is there an existing issue for this?
Current Behavior
No response
Expected Behavior
link to issue Fr-Dae#1
Steps To Reproduce
No response
Environment
Anything else?
No response
Upvote & Fund
The text was updated successfully, but these errors were encountered: