-
Notifications
You must be signed in to change notification settings - Fork 8
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
Relax username requirements a little #943
Relax username requirements a little #943
Conversation
Not sure why the tests are failing? Seems unrelated to the PR changes I think.. |
Yep, it's the db encryption, have commented out the volumes in the db part of the docker-compose for now and then it works |
Now you should be able to merge dev and then the tests should pass |
I don't have permissions to merge :) |
I meant merge |
So that the docker-compose change is in this too and the tests pass |
@ewels Could you also add an entry in the changelog? |
Codecov Report
@@ Coverage Diff @@
## dev #943 +/- ##
==========================================
+ Coverage 87.89% 87.90% +0.01%
==========================================
Files 26 26
Lines 2899 2894 -5
==========================================
- Hits 2548 2544 -4
+ Misses 351 350 -1
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just tested: Do we want to allow usernames containing all or almost all special characters?
If in doubt, copy what GitHub does..? 😀 https://github.com/shinnn/github-username-regex#github-username-regex
Actually quite restrictive.. Drop-in regex: Personally I'm happy with what's in this PR.. |
@ewels Ok I will add this as a possible future change since it's not a high priority, but I will approve and merge this PR now 👍🏻 |
Minor changes to username requirements, needs agreement in meeting:
.
and-
in usernamesdev
branch