Lines Matching +full:create +full:- +full:release

5 - [Introduction](#introduction)
6 - [Code of Conduct](#code-of-conduct)
7 - [Matrix Room](#matrix-room)
8 - [Reporting Bugs and Suggesting Improvements](#reporting-bugs-and-suggesting-improvements)
9 - [Contribution Workflow](#contribution-workflow)
10 - [Quality Standards](#quality-standards)
11 - [Release Process](#release-process)
30 Joining the matrix room at [#codespan:matrix.org][codespan-matrix] is a good way to get in touch wi…
32 [codespan-matrix]: https://app.element.io/#/room/#codespan:matrix.org
36 Bugs (unwanted behaviour) and suggested improvements are tracked as [GitHub issues][github-issues].
39 1. The issue is caused by `codespan-reporting` itself and not by how it is used.
43   Please look through the open issues in the [issue tracker][github-issues].
52 [github-issues]: https://github.com/brendanzab/codespan/issues
58 1. Make a fork of the [codespan repository][codespan-repo].
59 1. Within your fork, create a branch for your contribution. Use a meaningful name.
60 1. Create your contribution, meeting all [contribution quality standards](#quality-standards).
62 1. [Create a pull request][create-a-pr] against the `master` branch of the repository.
65 [codespan-repo]: https://github.com/brendanzab/codespan
66 [create-a-pr]: https://help.github.com/articles/creating-a-pull-request-from-a-fork/
73 - Separate each **logical change** into its own commit.
74 - Include tests for any new functionality and fixed issues in your pull request.
75 - Update the changelogs with any added, removed, changed, or fixed functionality.
76 - Document public functions.
77 - Format code with `cargo fmt`.
78 - Avoid adding `unsafe` code.
80 - Add a descriptive message for each commit.
81   Follow [these commit message guidelines][commit-messages].
82 - Document your pull requests.
85 [commit-messages]: https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html
87 ## Release Process
91 1. Create a new PR for the release, and if it passes CI merge it.
92 1. Create a new tag for the release, pointing to the merge commit.
95     due to a server-side delay in crate publishing:
97     cd codespan-reporting && cargo publish; cd ..
99     cd codespan-lsp && cargo publish; cd ..