@@ -19,11 +19,12 @@ Note: Some steps are OPTIONAL but all are RECOMMENDED.
1919 $ cd podman-compose
2020 ```
2121
22- 2 . (OPTIONAL) Create a Python virtual environment. Example using
23- [ virtualenv wrapper ] ( https://virtualenvwrapper.readthedocs.io/en/latest/ ) :
22+ 2 . (OPTIONAL) Create a Python virtual environment. Example using python builtin
23+ ` venv ` module :
2424
2525 ``` shell
26- $ mkvirtualenv podman-compose
26+ $ python3 -m venv .venv
27+ $ . .venv/bin/activate
2728 ```
2829
29303. Install the project runtime and development requirements:
@@ -60,9 +61,25 @@ Note: Some steps are OPTIONAL but all are RECOMMENDED.
6061 - Make sure you include a `Signed-off-by` message in your commits.
6162 Read [this guide](https://github.com/containers/common/blob/main/CONTRIBUTING.md#sign-your-prs)
6263 to learn how to sign your commits.
63- - In the commit message, reference the Issue ID that your code fixes and a brief description of
64- the changes.
65- Example: `Fixes #516: Allow empty network`
64+ - In the commit message body, reference the Issue ID that your code fixes and a brief description of the changes.
65+ Example:
66+ ```
67+ Allow empty network
68+
69+ <description, such as links to the compose spec and so on>
70+
71+ Fixes https://github.com/containers/podman-compose/issues/516
72+ ```
73+ - If your commit requires a refactoring, first do the refactoring and
74+ commit it separately before starting feature work. This makes the
75+ pull request easier to review. Additionally, pull request will be
76+ less risky, because if it breaks something, it' s way easier to
77+ isolate the offending code, understand what' s broken and fix it.
78+ Due to the latter reason it' s best to commit in as many independent
79+ commits as reasonable.
80+
81+ This will result in pull requests being merged much faster.
82+
66839. Open a pull request to ` containers/podman-compose` and wait for a maintainer to review your work.
6784
6885# # Adding new commands
0 commit comments