You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for your interest in contributing to this project!
3
+
Thank you for your interest in contributing to this project! We strive to make the contribution process clear and welcoming.
4
4
5
-
We want to make contributing as easy and transparent as possible.
5
+
Please take a moment to review the guidelines below.
6
6
7
7
8
8
## Code of Conduct
9
9
10
-
Our code of conduct is described in [CODE_OF_CONDUCT.md](CODE_OF_CONDUCT.md).
10
+
Please review and adhere to our [Code of Conduct](CODE_OF_CONDUCT.md) in all your interactions with the project.
11
+
This helps us maintain a positive and respectful environment for everyone involved.
11
12
12
13
13
-
## Issues
14
+
## How to Contribute
14
15
15
-
We use GitHub issues to track bugs and feature requests. Please ensure your description is clear and has sufficient instructions to be able to reproduce the issue.
16
+
### Contributor Responsibilities
16
17
18
+
By submitting your contributions, you agree to the following:
19
+
- You are the sole author of the content you contribute, or you have the appropriate rights and permissions to contribute it.
20
+
- If employed, you have obtained any necessary permissions from your employer to contribute to this project.
21
+
- All contributions will be made available under the project’s license.
17
22
18
-
##Pull Requests
23
+
### Issues
19
24
20
-
Before you make a substantial pull request, please file an issue and make sure someone from the team agrees that there is a problem or room for improvement.
25
+
We use GitHub Issues to track bugs and feature requests. When submitting an issue, please ensure:
26
+
- The description is clear and concise.
27
+
- You provide enough details and steps to reproduce the issue, if applicable.
21
28
29
+
### Pull Requests
22
30
23
-
## License
31
+
Before making substantial contributions:
32
+
1.**Discuss Changes**: Please file an issue first to discuss your proposed changes with the team. This helps ensure your contribution aligns with the project’s goals.
33
+
2.**Follow Best Practices**: Adhere to the guidelines and ensure your code meets the project’s standards (see [Code Guidelines](#code-guidelines)).
24
34
25
-
By contributing your code, you agree to license your contribution under the [Apache License 2.0](LICENSE.txt).
35
+
When submitting a pull request:
36
+
- Ensure your changes are well-documented.
37
+
- Include tests for any new features or significant changes.
38
+
- Reference the relevant issue(s) in your pull request description.
39
+
40
+
41
+
## Licensing
42
+
43
+
By contributing to this project, you agree that your contributions will be licensed under the [Apache License 2.0](LICENSE.txt).
44
+
45
+
The project itself is also licensed under the [Apache License 2.0](LICENSE.txt)).
run_step "Load image into local daemon for testing" @@ "
177
-
docker pull '$LOCAL_REGISTRY/$image_name';
178
-
docker tag '$LOCAL_REGISTRY/$image_name' '$image_name'
179
-
"
176
+
# cannot use "regctl image copy ... " which does not support loading into docker daemon https://github.com/regclient/regclient/issues/568
177
+
# cannot use "docker pull '$LOCAL_REGISTRY/$image_name'" which does not support ad-hoc pulling from unsecure registries - must be allowed in docker daemon config
178
+
run_step "Load image into local daemon for testing" -- \
179
+
docker run --rm \
180
+
-v /var/run/docker.sock:/var/run/docker.sock \
181
+
--network host `# required to access the temporary registry` \
0 commit comments