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
Copy file name to clipboardexpand all lines: .github/CONTRIBUTING.md
+12-8
Original file line number
Diff line number
Diff line change
@@ -2,20 +2,24 @@
2
2
3
3
Hi there! We're thrilled that you'd like to contribute to this project. Your help is essential for keeping it great.
4
4
5
-
Contributions to this project are [released](https://help.github.com/articles/github-terms-of-service/#6-contributions-under-repository-license) to the public under the [project's open source license](LICENSE).
5
+
Contributions to this project are [released](https://docs.github.com/en/github/site-policy/github-terms-of-service#6-contributions-under-repository-license)
6
+
to the public under the [project's open source license](LICENSE).
6
7
7
8
## Submitting a pull request
8
9
9
10
1.[Fork](https://github.com/docker/login-action/fork) and clone the repository
10
11
2. Configure and install the dependencies: `yarn install`
11
-
4. Create a new branch: `git checkout -b my-branch-name`
12
-
5. Make your change
13
-
6. Run pre-checkin: `yarn run pre-checkin`
14
-
7. Push to your fork and [submit a pull request](https://github.com/docker/login-action/compare)
15
-
8. Pat your self on the back and wait for your pull request to be reviewed and merged.
12
+
3. Create a new branch: `git checkout -b my-branch-name`
13
+
4. Make your changes
14
+
5. Make sure the tests pass: `docker buildx bake test`
15
+
6. Format code and build javascript artifacts: `docker buildx bake pre-checkin`
16
+
7. Validate all code has correctly formatted and built: `docker buildx bake validate`
17
+
8. Push to your fork and [submit a pull request](https://github.com/docker/login-action/compare)
18
+
9. Pat your self on the back and wait for your pull request to be reviewed and merged.
16
19
17
20
Here are a few things you can do that will increase the likelihood of your pull request being accepted:
18
21
22
+
- Write tests.
19
23
- Make sure the `README.md` and any other relevant **documentation are kept up-to-date**.
20
24
- We try to follow [SemVer v2.0.0](https://semver.org/). Randomly breaking public APIs is not an option.
21
25
- Keep your change as focused as possible. If there are multiple changes you would like to make that are not dependent upon each other, consider submitting them as **separate pull requests**.
@@ -24,5 +28,5 @@ Here are a few things you can do that will increase the likelihood of your pull
24
28
## Resources
25
29
26
30
-[How to Contribute to Open Source](https://opensource.guide/how-to-contribute/)
Copy file name to clipboardexpand all lines: .github/ISSUE_TEMPLATE/bug_report.md
+2-1
Original file line number
Diff line number
Diff line change
@@ -30,4 +30,5 @@ about: Create a report to help us improve
30
30
31
31
### Logs
32
32
33
-
> Download the [log file of your build](https://help.github.com/en/actions/configuring-and-managing-workflows/managing-a-workflow-run#downloading-logs) and [attach it](https://help.github.com/en/github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests) to this issue.
33
+
> Download the [log file of your build](https://docs.github.com/en/actions/managing-workflow-runs/using-workflow-run-logs#downloading-logs)
34
+
> and [attach it](https://docs.github.com/en/github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests) to this issue.
0 commit comments