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
+7-7Lines changed: 7 additions & 7 deletions
Original file line number
Diff line number
Diff line change
@@ -4,9 +4,9 @@ Contributing to Apache CloudStack (ACS)
4
4
Summary
5
5
-------
6
6
This document covers how to contribute to the ACS project. ACS uses GitHub PRs to manage code contributions.
7
-
These instructions assume you have a GitHub.com account, so if you don't have one you will have to create one. Your proposed code changes will be published to your own fork of the ACS project and you will submit a Pull Request for your changes to be added.
7
+
These instructions assume you have a GitHub.com account, so if you don't have one you will have to create one. Your proposed code changes will be published to your own fork of the ACS project, and you will submit a Pull Request for your changes to be added.
8
8
9
-
_Lets get started!!!_
9
+
_Let's get started!!!_
10
10
11
11
Bug fixes
12
12
---------
@@ -26,7 +26,7 @@ No back porting / cherry-picking features to existing branches!
26
26
27
27
PendingReleaseNotes file
28
28
------------------------
29
-
When developing a new feature or making a (major) change to a existing feature you are encouraged to append this to the PendingReleaseNotes file so that the Release Manager can
29
+
When developing a new feature or making a (major) change to an existing feature you are encouraged to append this to the PendingReleaseNotes file so that the Release Manager can
30
30
use this file as a source of information when compiling the Release Notes for a new release.
31
31
32
32
When adding information to the PendingReleaseNotes file make sure that you write a good and understandable description of the new feature or change which you have developed.
@@ -38,9 +38,9 @@ Fork the code
38
38
39
39
In your browser, navigate to: [https://github.com/apache/cloudstack](https://github.com/apache/cloudstack)
40
40
41
-
Fork the repository by clicking on the 'Fork' button on the top right hand side. The fork will happen and you will be taken to your own fork of the repository. Copy the Git repository URL by clicking on the clipboard next to the URL on the right hand side of the page under '**HTTPS** clone URL'. You will paste this URL when doing the following `git clone` command.
41
+
Fork the repository by clicking on the 'Fork' button on the top right hand side. The fork will happen, and you will be taken to your own fork of the repository. Copy the Git repository URL by clicking on the clipboard next to the URL on the right hand side of the page under '**HTTPS** clone URL'. You will paste this URL when doing the following `git clone` command.
42
42
43
-
On your computer, follow these steps to setup a local repository for working on ACS:
43
+
On your computer, follow these steps to set up a local repository for working on ACS:
When you are happy with your changes and you are ready to contribute them, you will create a Pull Request on GitHub to do so. This is done by pushing your local changes to your forked repository (default remote name is `origin`) and then initiating a pull request on GitHub.
95
+
When you are happy with your changes, and you are ready to contribute them, you will create a Pull Request on GitHub to do so. This is done by pushing your local changes to your forked repository (default remote name is `origin`) and then initiating a pull request on GitHub.
96
96
97
-
Please include JIRA id, detailed information about the bug/feature, what all tests are executed, how the reviewer can test this feature etc. Incase of UI PRs, a screenshot is preferred.
97
+
Please include JIRA id, detailed information about the bug/feature, what all tests are executed, how the reviewer can test this feature etc. In case of UI PRs, a screenshot is preferred.
98
98
99
99
> **IMPORTANT:** Make sure you have rebased your `feature_x` branch to include the latest code from `upstream/main`_before_ you do this.
0 commit comments