-
Notifications
You must be signed in to change notification settings - Fork 5
refactor(initial): [UDENG-5667] initalize and setup repository #1
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
refactor(initial): [UDENG-5667] initalize and setup repository #1
Conversation
- Only fix/add the functionality in question **OR** address wide-spread whitespace/style issues, not both. | ||
- Add unit or integration tests for fixed or changed functionality. | ||
- Address a single concern in the least number of changed lines as possible. | ||
- Include documentation in the repo or on our [docs site](https://github.com/ubuntu/Ubuntu-Insights/wiki). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are we using the GitHub wiki for documentation?
CONTRIBUTING.md
Outdated
|
||
Contributions are made to this project via Issues and Pull Requests (PRs). A few general guidelines that cover both: | ||
|
||
- To report security vulnerabilities, please use the advisories page of the repository and not a public bug report. Please use [launchpad private bugs](https://bugs.launchpad.net/ubuntu/+source/Ubuntu-Insights/+filebug) which is monitored by our security team. On ubuntu machine, it’s best to use `ubuntu-bug Ubuntu Insights` to collect relevant information. FIXME: snap? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unsure about this part.
value: > | ||
:warning: **Please do not report security vulnerabilities here** | ||
|
||
Be careful with sensitive information and security vulnerabilities. In order to report bugs that could contain |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unsure about this part
value: > | ||
:warning: **Please do not report security vulnerabilities here** | ||
|
||
Be careful with sensitive information and security vulnerabilities. In order to report bugs that could contain |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unsure for this part
The issue seems to be specific to the schema VSCode relies on, even though according to documentation, a string should be okay for the labels field.
b8d8ca2
to
7f78eb3
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks fine for bootstrapping the repo. Only comment I have is the inconsistent file endings. Should standardize that.
What do you mean by inconsistent file endings? |
i.e. Many of the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks pretty good, just some small things and questions from me
Co-authored-by: trevor-shoe <[email protected]>
@hk21702 There are still a bunch of file/line ending issues showing in the diff on github. |
I think GitHub just ignores the white space at the end of files in the diff. On my local clone, the new lines exist. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for humouring me and cleaning up the file endings!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
What about that commit @Patriot7865 ? |
Create basic project structure as well as adding initial basic GitHub Workflows.
The file structure is designed for three primary accessible components. The client-side, the server-side internet exposed service, and the server-side air gapped ingest service.
UDENG-5667