Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Readme typo #22

Open
macl-spindance opened this issue May 20, 2021 · 6 comments
Open

Readme typo #22

macl-spindance opened this issue May 20, 2021 · 6 comments

Comments

@macl-spindance
Copy link

macl-spindance commented May 20, 2021

Description of defect

The Readme says, "... to the Azure IoT Hub service". However this repo is for the AWS IoT core service. This is a simple bug report, yet the bot has requested that I pad out the description to 25 words. So there you go.

Target(s) affected by this defect ?

n/a

Toolchain(s) (name and version) displaying this defect ?

n/a

What version of Mbed-os are you using (tag or sha) ?

n/a

What version(s) of tools are you using. List all that apply (E.g. mbed-cli)

n/a

How is this defect reproduced ?

n/a

@ciarmcom
Copy link
Member

@macl-spindance thank you for raising this issue.Please take a look at the following comments:

Could you add some more detail to the description? A good description should be at least 25 words.

NOTE: If there are fields which are not applicable then please just add 'n/a' or 'None'. This indicates to us that at least all the fields have been considered.
Please update the issue header with the missing information, the issue will not be mirrored to our internal defect tracking system or investigated until this has been fully resolved.

@ciarmcom
Copy link
Member

@macl-spindance it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

@macl-spindance
Copy link
Author

Can a human review this ticket and kindly tell the bot that this is so simple it does not take 25 words to describe?

@ciarmcom
Copy link
Member

@macl-spindance it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

1 similar comment
@ciarmcom
Copy link
Member

ciarmcom commented Jun 4, 2021

@macl-spindance it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

@ciarmcom
Copy link
Member

ciarmcom commented Jun 7, 2021

Thank you for raising this detailed GitHub issue. I am now notifying our internal issue triagers.
Internal Jira reference: https://jira.arm.com/browse/IOTOSM-4053

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants