| #
f4febd00 |
| 08-Dec-2022 |
Patrick Williams <patrick@stwcx.xyz> |
prettier: re-format
Prettier is enabled in openbmc-build-scripts on Markdown, JSON, and YAML
files to have consistent formatting for these file types. Re-run the
formatter on the whole repository.
prettier: re-format
Prettier is enabled in openbmc-build-scripts on Markdown, JSON, and YAML
files to have consistent formatting for these file types. Re-run the
formatter on the whole repository.
Change-Id: I35ec9c19ae581e4dd00b515c1bba3a9c1862eeb1
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
show more ...
|
| #
c9fb5ea7 |
| 10-May-2022 |
Ed Tanous <edtanous@google.com> |
Require patches follow yocto upstreaming rules
For meta layer patches, Yocto has a well-formed process for handling
patches. While patches should ideally be avoided, for the patches we do
choose to
Require patches follow yocto upstreaming rules
For meta layer patches, Yocto has a well-formed process for handling
patches. While patches should ideally be avoided, for the patches we do
choose to maintain, we should follow the best practices that yocto
defines to make sure they're maintainable.
Signed-off-by: Ed Tanous <edtanous@google.com>
Change-Id: Ie75bf81bc31381a7eb036f4cbafd10b17fda8f19
show more ...
|
| #
d3b3bf70 |
| 09-Feb-2022 |
Ed Tanous <edtanous@google.com> |
Make guidelines more clear on public repos
Resolves openbmc/technical-oversight-forum#12.
Signed-off-by: Ed Tanous <edtanous@google.com>
Change-Id: Ic1ce65d00d3c9761b361fba0f33965f26bf82b80
|
| #
9746aeb8 |
| 22-Apr-2022 |
Brad Bishop <bradleyb@fuzziesquirrel.com> |
Make layer-guidelines a real markdown document
Add headers/anchors. This facilitates easy copy & paste of links to
specific sections of the document. Remove periods from new headers
because markdo
Make layer-guidelines a real markdown document
Add headers/anchors. This facilitates easy copy & paste of links to
specific sections of the document. Remove periods from new headers
because markdownlint doesn't allow that. Reword the EXTRA_OEMAKE
guideline so it fits on a single line.
Add bolding and linebreaks around **why?** and **What should I do
instead?**. The intent seems to have been to have these render on their
own line (bold and not H3 because markdownlint does not allow multiple
headings with the same content).
Add linebreaks in other places where the intent was for a new paragraph
to be rendered(I think?).
Change {autorev} to make it look more like it actually appears in the
code.
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
Change-Id: Ib49d9e1079ff3a8b27c788ae34e1868a01cffc8f
show more ...
|
| #
d078e0d2 |
| 04-Feb-2021 |
Ed Tanous <edtanous@google.com> |
Try to document our meta layer guidelines
Most of the meta layer guidelines have been unwritten "rules". This
commit tries to write them down.
Signed-off-by: Ed Tanous <edtanous@google.com>
Change
Try to document our meta layer guidelines
Most of the meta layer guidelines have been unwritten "rules". This
commit tries to write them down.
Signed-off-by: Ed Tanous <edtanous@google.com>
Change-Id: I8687393fea56be5e68d10bbf42183f8797119b4b
show more ...
|