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: CONTRIBUTING.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,7 @@ We welcome contributions of all kinds:
15
15
## Getting Started
16
16
17
17
### Ask Questions or Discuss Ideas
18
-
- Join our community on [Slack](http://slack.litmuschaos.io) and post in **#litmus** for general questions or **#litmus-dev** for technical discussions.
18
+
- Join our community on [Slack](https://slack.litmuschaos.io) and post in **#litmus** for general questions or **#litmus-dev** for technical discussions.
19
19
20
20
### Report Issues or Propose Changes
21
21
- Open a new [GitHub issue](https://github.com/litmuschaos/litmus/issues/new) describing your request, bug, or feature idea.
@@ -27,7 +27,7 @@ We welcome contributions of all kinds:
27
27
-**Manual setup**
28
28
Follow the [Local Development Guide](https://github.com/litmuschaos/litmus/wiki/ChaosCenter-Development-Guide) if you prefer to set up and configure the environment yourself.
29
29
- Review [Development Best Practices](https://github.com/litmuschaos/litmus/wiki/Development-Best-Practices)
30
-
- For Go contributors, read [Effective Go](https://golang.org/doc/effective_go.html) and [Go Code Review Comments](https://go.dev/wiki/CodeReviewComments)
30
+
- For Go contributors, read [Effective Go](https://go.dev/doc/effective_go) and [Go Code Review Comments](https://go.dev/wiki/CodeReviewComments)
31
31
32
32
You can contribute fixes and improvements by submitting a Pull Request (PR) on GitHub. Each PR will be reviewed by one or more maintainers and merged once it meets the project’s standards.
33
33
@@ -64,8 +64,8 @@ For full details, see the [DCO documentation](https://developercertificate.org/)
- If you are making any changes in backend, make sure you have run and tested the code locally, the reviewers might ask for relevant screenshots in the comments.
71
71
- Include relevant tests for new code or bug fixes
@@ -82,7 +82,7 @@ For full details, see the [DCO documentation](https://developercertificate.org/)
82
82
- Merge occurs when all checks pass and reviews are approved
83
83
- If your PR is large or high-impact, coordinate with maintainers in **#litmus-dev** Slack
84
84
85
-
If you are new to Go, consider reading [Effective Go](https://golang.org/doc/effective_go.html) and [Go Code Review Comments](https://github.com/golang/go/wiki/CodeReviewComments) for guidance on writing idiomatic Go code.
85
+
If you are new to Go, consider reading [Effective Go](https://go.dev/doc/effective_go) and [Go Code Review Comments](https://go.dev/wiki/CodeReviewComments) for guidance on writing idiomatic Go code.
86
86
87
87
## Pull Request Checklist
88
88
-[ ] Rebase to the current master branch before submitting your pull request.
0 commit comments