summaryrefslogtreecommitdiff
path: root/HACKING.rst
AgeCommit message (Collapse)Author
2020-04-23More unit test documentation (#314)Daniel Watkins
* HACKING.rst: add list of available pytest fixtures * HACKING.rst: capture common mock naming pattern in codebase
2020-04-14HACKING.rst: add pytest version gotchas section (#311)Daniel Watkins
And document that we can't yield in pytest.fixture functions due to the age of xenial's pytest.
2020-03-31HACKING.rst: reorganise/update CLA signature info (#297)Daniel Watkins
* Split the "existing contributors" information out to a separate section * Update the "Do these things once" CLA information for the current process
2020-03-31HACKING.rst: add note about variable annotations (#295)Daniel Watkins
2020-03-30HACKING.rst: add Type Annotations design section (#293)Daniel Watkins
2020-03-26HACKING.rst: add examples of the two test class types (#278)Daniel Watkins
2020-03-25HACKING.rst: add Unit Testing design section (#277)Daniel Watkins
2020-03-24HACKING.rst: add links to new Code Review Process doc (#276)Daniel Watkins
Co-authored-by: Joshua Powers <josh.powers@canonical.com>
2020-01-29HACKING.rst: update CLA link (#199)Daniel Watkins
2019-12-19HACKING.rst: clarify that everyone needs to do the LP->GH dance (#130)Daniel Watkins
The previous language suggested that only people who had signed the CLA previously needed to prove their GH identity, which is not the case.
2019-12-17doc: specify _ over - in cloud config modulesJoshua Powers
Start a design decision area in HACKING to capture highlevel decisions. First example is to capture the use of _ over - in cloud config modules. LP: #1293254
2019-11-07doc: update launchpad git refs to githubRyan Harper
2018-12-18HACKING.rst: change contact info to Josh PowersScott Moser
In the Hacking doc, change the contact information for the contributors agreement to reference Josh Powers rather than Scott Moser.
2018-01-25HACKING.rst: mention setting user name and email via git config.Scott Moser
Just include mention of setting user name and email when first setting up git.
2017-04-12HACKING.rst: more info on filling out contributors agreement.Scott Moser
When signing the Contributors agreement, the user is prompted to provide a 'Project contact' or 'Canonical Project Manager'. Just update the HACKING.rst document to tell them what to put there.
2016-11-10doc: make the RST files consistently formated and other improvements.Scott Moser
The biggest things here are: * move doc/sources/*/README.rst to doc/rtd/topics/datasources This gives each datasource a page in the rtd docs, which make it easier to read. * consistently use the same header style throughout. As suggested at http://thomas-cokelaer.info/tutorials/sphinx/rest_syntax.html use: # with overline, for parts * with overline, for chapters =, for sections -, for subsections ^, for subsubsections “, for paragraphs Also, move and re-format vendor-data documentation to rtd.
2016-11-01doc: improve HACKING.rst fileScott Moser
Put a bit more information and a few style fixes in HACKING.rst.
2016-08-03Update build tools to work with gitLars Kellogg-Stedman
- Update HACKING.rst to include git instructions - update MANIFEST.in and .gitignore to ignore git-related things - replaced tarball generation scripts with git-based script - have the spec files correctly identify themselves as cheetah templates - make brpm work with git
2014-08-26Remove pylintJay Faulkner
pylint was not passing, and per smoser in IRC pylint can/should be removed.
2013-02-04Add initial docs about datasources.harlowja
Start moving the current README for datasources to a RST format and include those files in the rtd site. LP: #1113650