|Version 1 (modified by 5 weeks ago) ( diff ),|
If you feel like contributing there are a couple of ways to do this
- You can add new super high speed bash code, optimizing existing, rewrite for broader support of bash environments across OS's
- You can add domains to either the wildcard.list or domain.list in there respective folders
- You can through Damned good arguments try to get a domain into the whitelisted
The workflow is a bit clumsy, but the most reliable and simple.
- You add an issue, and describing your submission.
- You then open a MR (Merge Request) where you'll add you contribution
- Add PR_ID and Issue_ID and the domain_name in the commit message
git commit -S -am "!PrID #IssueID `example.com`"
Why first issue then MR?
The simplest idea is often the most safe, and this is the very reason for this workflow. It is also giving the project a searchable database for added domains and the comment, by which we can't add in other ways, as all the lists needs to be raw data; from which other scripts easily can work with, without first have to run several cleanup processes.
We require all submissions to be signed with a valid GPG key.
Only exception for this rule is the CI/CD bot
How do I sign with GPG
If you know nothing about GPG keys, I really suggest you search on duckduckgo.com for the best way, to do it for the OS you are using.
However if you do have a GPG key, add it to you submission profile and add a
git commit -S -m "Some very cool enhancements" and that's is. You can also
set this globally or pr git. Do a search on duckduckgo.com
to figure out the current way.
- All files most end with a newline (\n)(LF) UTF-8.
- All files have to be in universal UTF-8 style without BOM.
- Files containing
_windows_in it's filename most be encoded in
ISO-8859-1Latin1 and newlines shall end in (CRLF).
- Line length should not be more than 80 chars for terminals support.