Skip to content

Fix: Allow issues to be submitted using the user's GitHub username in Collabocate #1

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

Open
wants to merge 6 commits into
base: develop
Choose a base branch
from

Conversation

samuko-things
Copy link
Contributor

This pull request makes the following changes

General checklist

  • My pull request adheres to the Collabo Community pull request guidelines.
  • I have read and understood the Pull request guideline extension section found at the bottom of this pull request description/body.
  • I have replaced the dummy text under the subheading Testing checklist below with the testing checklist from the issue ticket I'm working on.

Testing checklist

  • Users that have GitHub account and authorized Github to use it, are now able to submit issue tickets with their own user name on the issue, to show that they authored it.
  • Users that do not have a GitHub account or that didn't specify/authorize GitHub to use their account, retain the use of @collabo-user as the author of the issue ticket, to show it's by anonymous user.
  • I certify that I ran my checklist

Pull request guideline extension

Note

Do not remove this note or section. This talks about extra things to take note of, in addition to the directions given in the Collabo Community pull request guidelines.

We appreciate the time taken to help tackle issue tickets within the Collabo Community. Please go ahead to submit your pull request even if it is not yet completed, and push to the pull request actively. This will allow us to know that you have not abandoned the issue ticket. However, you should only alert reviewers about your pull request as explained below, to avoid flooding their GitHub notifications unnecessarily.

"Ready for review" implies that things are working as expected, according to how it is specified in the issue ticket you are working on. Ensure that you test the code that you are working on, that it works as expected. Don't just request for review when your pull request is not yet done and working.

The only time you should be making people review something incomplete is: if you want to show them what's not working, so that they can send help or guidance. If this is the case, be explicit about this in our Discord community or in the comment of your pull request (after you have submitted the pull request).

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.

Allow issues to be submitted using the user's GitHub username in Collabocate
1 participant