WissKI Rules

Rules for wiki authors

• always link unknown terms to the glossary
• create a separate page in the Glossary folder for each term in the glossary

Issue Rules

Check in Issues for WissKI if your problem already exists (and had been solved).

Create new issues with Drupal issue tracker

fill the mandatory fields like Title, Project, Category, Priority, Status, Version, Component, Assigned. Remember to choose the correct development version, i.e. 8.x-4.x.

Provide some tags and speaking summary.

Click Save.

Click Create issue fork. You may want to choose a custom fork name.

Add & fetch this issue fork’s repository to your existing WissKI git.

git remote add <fork name> git@git.drupal.org:issue/<fork name>.git
git fetch <fork name>

The commands are provided by the drupal interface after creating a new issue fork. Click on Show commands to see something like:

git remote add wisski-3544557 git@git.drupal.org:issue/wisski-3544557.git
git fetch wisski-3544557

In this case the provided fork name is wisski-3544557.

Create new branch in fork by clicking Create new branch.

Choose a fork branch name, in this case we chose 3544557-update-docs for the \<fork branch name>.

Switch to fork branch.

git checkout -b <fork branch name> --track <fork name>/<fork branch name>

Example with this :

git checkout -b '3544557-update-docs' --track wisski-3544557/'3544557-update-docs'

Do your changes and commit.

git add <files that changed>
git commit -m "<your commit message>"

Push to fork repository.

git push <fork branch name>