Lines Matching +full:stale +full:- +full:issue +full:- +full:label

1 <!-- Copyright 2022 The Fuchsia Authors
3 Licensed under a BSD-style license <LICENSE-BSD>, Apache License, Version 2.0
4 <LICENSE-APACHE or https://www.apache.org/licenses/LICENSE-2.0>, or the MIT
5 license <LICENSE-MIT or https://opensource.org/licenses/MIT>, at your option.
7 those terms. -->
14 Once you've read the rest of this doc, check out our [good-first-issue
15 label][good-first-issue] for some good issues you can use to get your toes wet!
46 In non-library code, it's often advised to only implement features you need.
53 Thus, when designing external-facing features, try to make use of them somehow.
62 probably is! Invest the time to find the root cause - you will either learn
80 Documentation comments should be self-contained; in other words, do not assume
87 Phrase your comments to avoid references that might become stale; for example:
96 1. Include an issue reference using the format `TODO(#123):`
99    sources, including the referenced issue.
108 1. Tests must be deterministic. Threaded or time-dependent code, random number
137 Commit messages should be _concise_ but self-contained (avoid relying on issue
146 1. [Separate subject from body with a blank line](https://chris.beams.io/posts/git-commit/#separate)
147 1. [Limit the subject line to 50 characters](https://chris.beams.io/posts/git-commit/#limit-50)
148 1. [Capitalize the subject line](https://chris.beams.io/posts/git-commit/#capitalize)
149 1. [Do not end the subject line with a period](https://chris.beams.io/posts/git-commit/#end)
150 1. [Use the imperative mood in the subject line](https://chris.beams.io/posts/git-commit/#imperativ…
151 1. [Wrap the body at 72 characters](https://chris.beams.io/posts/git-commit/#wrap-72)
152 1. [Use the body to explain what and why vs. how](https://chris.beams.io/posts/git-commit/#why-not-…
157 zerocopy-derive crate:
163 The body may be omitted if the subject is self-explanatory; e.g. when fixing a
168 Commit messages should make use of issue integration. Including an issue
170 reference to the referenced issue, and will also make it so that the referenced
171 issue back-links to the commit. Use "Closes", "Fixes", or "Resolves" on its own
172 line to automatically close an issue when your commit is merged:
180 When using issue integration, don't omit necessary context that may also be
181 included in the relevant issue (see "Commit messages should be _concise_ but
182 self-contained" above). Git history is more likely to be retained indefinitely
183 than issue history (for example, if this repository is migrated away from GitHub
189 1. Non-public URLs
192     + Refer to commits in this repository by their SHA-1 hash
202 [about_pull_requests]: https://help.github.com/articles/about-pull-requests/
203 [beams_git_commit]: https://chris.beams.io/posts/git-commit/
204 [cargo_example]: http://xion.io/post/code/rust-examples.html
205 [change_detector_tests]: https://testing.googleblog.com/2015/01/testing-on-toilet-change-detector-t…
207 [commit_guidelines]: https://www.git-scm.com/book/en/v2/Distributed-Git-Contributing-to-a-Project#_…
208 [determinism]: https://fuchsia.dev/fuchsia-src/contribute/testing/best-practices#write_reproducible…
209 [flutter_philosophy]: https://github.com/flutter/flutter/wiki/Style-guide-for-Flutter-repo#philosop…
210 [good-first-issue]: https://github.com/google/zerocopy/issues?q=is%3Aissue+is%3Aopen+label%3A%22goo…
213 [miri]: https://github.com/rust-lang/miri
215 [undefined_behavior]: https://raphlinus.github.io/programming/rust/2018/08/17/undefined-behavior.ht…