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
+15-17
Original file line number
Diff line number
Diff line change
@@ -11,7 +11,7 @@ information to effectively respond to your bug report or contribution.
11
11
12
12
We welcome you to use the GitHub issue tracker to report bugs or suggest features.
13
13
14
-
When filing an issue, please check existing open, or recently closed, issues to make sure somebody else hasn't already
14
+
When filing an issue, please check [existing open](https://github.com/FreeRTOS/coreMQTT/issues), or [recently closed](https://github.com/FreeRTOS/coreMQTT/issues?q=is%3Aissue+is%3Aclosed), issues to make sure somebody else hasn't already
15
15
reported the issue. Please try to include as much information as you can. Details like these are incredibly useful:
16
16
17
17
* A reproducible test case or series of steps
@@ -24,28 +24,26 @@ reported the issue. Please try to include as much information as you can. Detail
24
24
Contributions via pull requests are much appreciated. Before sending us a pull request, please ensure that:
25
25
26
26
1. You are working against the latest source on the *main* branch.
27
-
2. You check existing open, and recently merged, pull requests to make sure someone else hasn't addressed the problem already.
28
-
3. You open an issue to discuss any significant work - we would hate for your time to be wasted.
27
+
1. You check existing open, and recently merged, pull requests to make sure someone else hasn't addressed the problem already.
28
+
1. You open an issue to discuss any significant work - we would hate for your time to be wasted.
29
29
30
30
To send us a pull request, please:
31
31
32
-
1. Ensure you are considering a change to AWS source code (FreeRTOS kernel, AWS libraries). Proposed changes to 3rd party code should be submitted instead to the 3rd party.
33
-
2. Fork the repository.
34
-
3. Modify the source; please focus on the specific change you are contributing. If you also reformat all the code, it will be hard for us to focus on your change.
35
-
4. Ensure local tests pass.
36
-
5. Commit to your fork using clear commit messages.
37
-
6. Send us a pull request, answering any default questions in the pull request interface.
38
-
7. Pay attention to any automated CI failures reported in the pull request, and stay involved in the conversation.
32
+
1. Fork the repository.
33
+
1. Modify the source; please focus on the specific change you are contributing. If you also reformat all the code, it will be hard for us to focus on your change.
34
+
1. Ensure that your contributions conform to the [style guide](https://docs.aws.amazon.com/embedded-csdk/202011.00/lib-ref/docs/doxygen/output/html/guide_developer_styleguide.html).
35
+
1. Format your code with uncrustify, using the config available in [FreeRTOS/CI-CD-Github-Actions](https://github.com/FreeRTOS/CI-CD-Github-Actions/blob/main/formatting/uncrustify.cfg).
36
+
1. Ensure local tests pass.
37
+
1. Commit to your fork using clear commit messages.
38
+
1. Send us a pull request, answering any default questions in the pull request interface.
39
+
1. Pay attention to any automated CI failures reported in the pull request, and stay involved in the conversation.
39
40
40
41
GitHub provides additional document on [forking a repository](https://help.github.com/articles/fork-a-repo/) and
41
42
[creating a pull request](https://help.github.com/articles/creating-a-pull-request/).
42
43
43
-
## Getting Your Pull Request Merged
44
-
All Pull Requests must be approved by our review team before it can be merged in. We appreciate your patience while pull requests are reviewed as the time taken will depend on its complexity and wider implications.
45
-
46
44
47
45
## Finding contributions to work on
48
-
Looking at the existing issues is a great way to find something to contribute on. As our projects, by default, use the default GitHub issue labels (enhancement/bug/duplicate/help wanted/invalid/question/wontfix), looking at any 'help wanted' issues is a great place to start.
46
+
Looking at the existing issues is a great way to find something to contribute on. As our projects, by default, use the default GitHub issue labels ((enhancement/bug/duplicate/help wanted/invalid/question/wontfix), looking at any ['help wanted'](https://github.com/FreeRTOS/coreMQTT/labels?q=help+wanted) issues is a great place to start.
49
47
50
48
51
49
## Code of Conduct
@@ -55,11 +53,11 @@ [email protected] with any additional questions or comments.
55
53
56
54
57
55
## Security issue notifications
58
-
If you discover a potential security issue in this project we ask that you notify AWS/Amazon Security via our [vulnerability reporting page](http://aws.amazon.com/security/vulnerability-reporting/). Please do **not** create a public github issue.
56
+
If you discover a potential security issue in this project we ask that you notify AWS/Amazon Security via our [vulnerability reporting page](https://aws.amazon.com/security/vulnerability-reporting/). Please do **not** create a public github issue.
59
57
60
58
61
59
## Licensing
62
60
63
-
See the LICENSE file for our project's licensing. We will ask you to confirm the licensing of your contribution.
61
+
See the [LICENSE](../LICENSE) file for our project's licensing. We will ask you to confirm the licensing of your contribution.
64
62
65
-
We may ask you to sign a [Contributor License Agreement (CLA)](http://en.wikipedia.org/wiki/Contributor_License_Agreement) for larger changes.
63
+
We may ask you to sign a [Contributor License Agreement (CLA)](https://en.wikipedia.org/wiki/Contributor_License_Agreement) for larger changes.
Copy file name to clipboardexpand all lines: AWSSetup.md
+4-4
Original file line number
Diff line number
Diff line change
@@ -4,12 +4,12 @@ In case you already have an AWS account and user created, you can skip steps 1 a
4
4
## 1 Sign up for an AWS account
5
5
6
6
1. Open https://portal.aws.amazon.com/billing/signup.
7
-
2. Follow the online instructions. **NOTE:** Part of the sign-up procedure involves receiving a phone call and entering a verification code on the phone keypad.
7
+
2. Follow the online instructions. **NOTE:** Part of the sign-up procedure involves receiving a phone call and entering a verification code on the phone keypad.
8
8
3. Make a note of your AWS account number as it will be needed for the following steps.
9
9
10
10
## 2 Create an Administrator IAM user and grant it permissions
11
11
12
-
It’s strongly recommended that you adhere to the best practice of using the `Administrator` IAM user. The following steps show you how to create and securely lock away the root user credentials. One should only sign in as the root user to perform a few [account and service management tasks](https://docs.aws.amazon.com/general/latest/gr/root-vs-iam.html#aws_tasks-that-require-root).
12
+
It’s strongly recommended that you adhere to the best practice of using the `Administrator` IAM user. The following steps show you how to create and securely lock away the root user credentials. One should only sign in as the root user to perform a few [account and service management tasks](https://docs.aws.amazon.com/general/latest/gr/root-vs-iam.html#aws_tasks-that-require-root).
13
13
14
14
1. Sign in to the [IAM console](https://console.aws.amazon.com/iam/) as the account owner by choosing **Root user** and entering your AWS account email address. On the next page, enter your password.
15
15
2. On the navigation bar, click your account name, and then click Account.
@@ -31,7 +31,7 @@ It’s strongly recommended that you adhere to the best practice of using the `A
8. For **User name**, enter `Administrator`. Select the check box next to **AWS Management Console access**. Then select **Custom password**, and then enter your new password in the text box.
34
+
8. For **User name**, enter `Administrator`. Select the check box next to **AWS Management Console access**. Then select **Custom password**, and then enter your new password in the text box.
35
35
9. (Optional) By default, AWS requires the new user to create a new password when first signing in. You can clear the check box next to **User must create a new password at next sign-in** to allow the new user to reset their password after they sign in.
0 commit comments