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: CODE_OF_CONDUCT.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -1,10 +1,10 @@
1
1
# Contributor Code of Conduct
2
2
3
-
As contributors and maintainers of the MRSK project, we pledge to create a welcoming and inclusive environment for everyone. We value the participation of each member of our community and want all contributors to feel respected and valued.
3
+
As contributors and maintainers of the Kamal project, we pledge to create a welcoming and inclusive environment for everyone. We value the participation of each member of our community and want all contributors to feel respected and valued.
4
4
5
5
We are committed to providing a harassment-free experience for everyone, regardless of gender, gender identity and expression, sexual orientation, disability, physical appearance, body size, race, age, or religion (or lack thereof). We do not tolerate harassment of participants in any form.
6
6
7
-
This code of conduct applies to all MRSK project spaces, including but not limited to project code, issue trackers, chat rooms, and mailing lists. Violations of this code of conduct may result in removal from the project community.
7
+
This code of conduct applies to all Kamal project spaces, including but not limited to project code, issue trackers, chat rooms, and mailing lists. Violations of this code of conduct may result in removal from the project community.
Copy file name to clipboardexpand all lines: CONTRIBUTING.md
+11-11
Original file line number
Diff line number
Diff line change
@@ -1,18 +1,18 @@
1
-
# Contributing to MRSK development
1
+
# Contributing to Kamal development
2
2
3
-
Thank you for considering contributing to MRSK! This document outlines some guidelines for contributing to this open source project.
3
+
Thank you for considering contributing to Kamal! This document outlines some guidelines for contributing to this open source project.
4
4
5
-
Please make sure to review our [Code of Conduct](CODE_OF_CONDUCT.md) before contributing to MRSK.
5
+
Please make sure to review our [Code of Conduct](CODE_OF_CONDUCT.md) before contributing to Kamal.
6
6
7
7
There are several ways you can contribute to the betterment of the project:
8
8
9
-
-**Report an issue?** - If the issue isn’t reported, we can’t fix it. Please report any bugs, feature, and/or improvement requests on the [MRSK GitHub Issues tracker](https://github.com/mrsked/mrsk/issues).
10
-
-**Submit patches** - Do you have a new feature or a fix you'd like to share? [Submit a pull request](https://github.com/mrsked/mrsk/pulls)!
11
-
-**Write blog articles** - Are you using MRSK? We'd love to hear how you're using it with your projects. Write a tutorial and post it on your blog!
9
+
-**Report an issue?** - If the issue isn’t reported, we can’t fix it. Please report any bugs, feature, and/or improvement requests on the [Kamal GitHub Issues tracker](https://github.com/basecamp/kamal/issues).
10
+
-**Submit patches** - Do you have a new feature or a fix you'd like to share? [Submit a pull request](https://github.com/basecamp/kamal/pulls)!
11
+
-**Write blog articles** - Are you using Kamal? We'd love to hear how you're using it with your projects. Write a tutorial and post it on your blog!
12
12
13
13
## Issues
14
14
15
-
If you encounter any issues with the project, please check the [existing issues](https://github.com/mrsked/mrsk/issues) first to see if the issue has already been reported. If the issue hasn't been reported, please open a new issue with a clear description of the problem and steps to reproduce it.
15
+
If you encounter any issues with the project, please check the [existing issues](https://github.com/basecamp/kamal/issues) first to see if the issue has already been reported. If the issue hasn't been reported, please open a new issue with a clear description of the problem and steps to reproduce it.
16
16
17
17
## Pull Requests
18
18
@@ -33,17 +33,17 @@ A good commit message should describe what changed and why.
33
33
34
34
## Development
35
35
36
-
The `main` branch is regularly built and tested, but it is not guaranteed to be completely stable. Tags are created regularly from release branches to indicate new official, stable release versions of MRSK.
36
+
The `main` branch is regularly built and tested, but it is not guaranteed to be completely stable. Tags are created regularly from release branches to indicate new official, stable release versions of Kamal.
37
37
38
-
MRSK is written in Ruby. You should have Ruby 3.2+ installed on your machine in order to work on MRSK. If that's already setup, run `bundle` in the root directory to install all dependencies. Then you can run `bin/test` to run all tests.
38
+
Kamal is written in Ruby. You should have Ruby 3.2+ installed on your machine in order to work on Kamal. If that's already setup, run `bundle` in the root directory to install all dependencies. Then you can run `bin/test` to run all tests.
39
39
40
40
1. Fork the project repository.
41
41
2. Create a new branch for your contribution.
42
42
3. Write your code or make the desired changes.
43
43
4.**Ensure that your code passes the project's minitests by running ./bin/test.**
44
44
5. Commit your changes and push them to your forked repository.
45
-
6.[Open a pull request](https://github.com/mrsked/mrsk/pulls) to the main project repository with a detailed description of your changes.
45
+
6.[Open a pull request](https://github.com/basecamp/kamal/pulls) to the main project repository with a detailed description of your changes.
46
46
47
47
## License
48
48
49
-
MRSK is released under the MIT License. By contributing to this project, you agree to license your contributions under the same license.
49
+
Kamal is released under the MIT License. By contributing to this project, you agree to license your contributions under the same license.
0 commit comments