Contributing¶
Thank you for contributing.
Reporting¶
Bugs and feature requests go to the issues of the library.
A security problem is not an issue. Do not open a public issue, pull request or discussion for one:
doing so hands a working exploit to every user of the library before a fix exists. Report it privately,
either through
GitHub private vulnerability reporting or
by email to security AT spomky-labs.com. The
security policy says what a report should contain
and what happens next.
The code¶
Pull requests go to the branch of the maintained line, which
RELEASES.md
names.
- Write or update tests. A fix without a test that fails before it is not a fix.
- The test suite, the coding standards, the static analysis and the mutation testing all run in the
project QA container, through Castor:
castor qaruns the lot, andcastor phpunitthe tests alone. - Rebase your branch before you open the pull request, and write commit messages that say what changed and why. You may be asked to squash.
The code of conduct applies to every exchange.
This documentation¶
The pages live in their own repository, web-auth/cose-doc. The pencil at the top right of a page opens it for editing on the branch of the version you are reading.
git clone https://github.com/web-auth/cose-doc.git
cd cose-doc
make install # the toolchain, in .venv
make serve # http://127.0.0.1:8000, rebuilt as you save
make check # the strict build continuous integration runs
make check is the gate: a broken internal link, an anchor that does not exist, a page absent from the
navigation or a navigation entry without a page fails the build.
One branch of that repository is one version of the library, named like its maintenance branch. A correction that applies to every version is made on the oldest maintained branch and merged forward.
Titles are in sentence case; names keep their capitals. Every code block is expected to run against the version the page documents.