Changeset e3f09a5 in matrix


Ignore:
Timestamp:
2020-01-16T04:16:10+01:00 (6 weeks ago)
Author:
Spirillen Marsupilami <3728965-spirillen@…>
Branches:
master
Children:
cb3da8b
Parents:
ef7ae0a
Message:

Typos and new links to functions [skip ci]

File:
1 edited

Legend:

Unmodified
Added
Removed
  • CONTRIBUTING.md

    ref7ae0a re3f09a5  
    33If you feel like contributing there are a couple of ways to do this
    44
    5 1. You can add new super high speed bash code, optimising existing, rewrite for
     51. You can add new super high speed bash code, optimizing existing, rewrite for
    66    broader support of bash environments across OS's
    771. You can add domains to either the wildcard.list or domain.list in there
    88    respective folders
    9 1. You can through **Damned** arguments try to get a domain into the whitelist
    10     folder
     91. You can through **Damned** good arguments try to get a domain into the
     10    whitelisted
    1111
    1212# Workflow
    1313
    1414The workflow is a bit clumsy, but the most reliable and simple.
    15 1. You add an issue, describing your submission
    16 1. You then open a MR (Merge Request) where you'll add you contribution
    17 1. Add PR_ID and Issue_ID and the domain_name in the commit massege
     151. You add an [issue](issues/new), and describing your submission.
     161. You then open a [MR](/merge_requests/new) (Merge Request) where you'll add you contribution
     171. Add PR_ID and Issue_ID and the domain_name in the commit message
    1818   ```shell
    19    git commin -S -am "!PrID #IssueID `exsample.com`"
     19   git commit -S -am "!PrID #IssueID `exsample.com`"
    2020   ```
    2121
    22 ## Why first issue then MR
    23 The simplest idea is often the most safe, and this is the very reason to this
     22## Why first issue then MR?
     23The simplest idea is often the most safe, and this is the very reason for this
    2424workflow. It is also giving the project a searchable database for added domains
    25 for comment, by which we can't add in other ways, as all the lists needs to be
    26 raw data; from which other scripts easily can work with, without first have to
    27 run several cleanup processes.
     25and the comment, by which we can't add in other ways, as all the lists needs to
     26be raw data; from which other scripts easily can work with, without first have
     27to run several cleanup processes.
    2828
    2929# GPG signed
    3030We require all submissions to be signed with a valid GPG key.
    3131
    32 Only exception to this rule is the CI/CD bot
     32Only exception for this rule is the CI/CD bot
    3333
    3434## How do I sign with GPG
    35 If you no nothing about GPG keys I really suggest you search on
    36 [duckduckgo](https://duckduckgo.com) for the best way to do it for the OS you
     35If you know nothing about GPG keys I, really suggest you search on
     36[duckduckgo.com](https://duckduckgo.com) for the best way, to do it for the OS you
    3737are using.
    3838
    39 However if you do have a GPG key, add it to you submission profile add at a `-S`
     39However if you do have a GPG key, add it to you submission profile and add a `-S`
    4040to `git commit -S -m "Some very cool enhancements"` and that's is. You can also
    41 set this globally or pr git. Do a search on [duckduckgo](https://duckduckgo.com)
     41set this globally or pr git. Do a search on [duckduckgo.com](https://duckduckgo.com)
    4242to figure out the current way.
    4343
    4444# Writing files/lines
    45 - All files most end with a newline (\n)(LF) UTF-8.
     45- All files most end with a newline `\n` (LF) UTF-8.
    4646- All files have to be in universal UTF-8 style without BOM
    47 - Files containing `_windows_` in it's files most be encoded in `ISO-8859-1`
    48   Latin1 and newlines shall end in (CRLF)
    49 - Line length should not be more than 80 chars for terminals support
     47- Files containing `_windows_` in it's filename most be encoded in `ISO-8859-1`
     48  Latin1 and newlines shall end in (CRLF).
     49- Line length should not be more than 80 chars for terminals support.
Note: See TracChangeset for help on using the changeset viewer.