MkPullRequestGuidelines
Node showing pull request guidelines.¶
Bases: MkTemplate
Name | Children | Inherits |
---|---|---|
MkTemplate mknodes.templatenodes.mktemplate Node representing a jinja template. |
graph TD
94596169003120["mkpullrequestguidelines.MkPullRequestGuidelines"]
94596168228624["mktemplate.MkTemplate"]
94596169139824["mkcontainer.MkContainer"]
94596169136704["mknode.MkNode"]
94596171773984["node.Node"]
139930746687680["builtins.object"]
94596168228624 --> 94596169003120
94596169139824 --> 94596168228624
94596169136704 --> 94596169139824
94596171773984 --> 94596169136704
139930746687680 --> 94596171773984
/home/runner/work/mknodes/mknodes/mknodes/templatenodes/mkpullrequestguidelines/metadata.toml
[metadata]
name = "MkPullRequestGuidelines"
icon = "octicon:git-pull-request-24"
group = "documentation"
# [examples.regular]
# title = "Regular"
# jinja = """
# {{ mk.MkPullRequestGuidelines() }}
# """
[output.markdown]
template = """
Link to any related issue in the Pull Request message.
During the review, we recommend using fixups:
{{ "git commit --fixup=SHA # SHA of commit you want to fix" | MkCode }}
Once all the changes are approved, you can squash your commits:
{{ "git rebase -i --autosquash main" | MkCode }}
And force-push:
{{ "git push -f" | MkCode }}
If this seems all too complicated, you can push or force-push each new commit,
and we will squash them ourselves if needed, before merging.
"""