Skip to content

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

Merged

Conversation

hk21702
Copy link
Collaborator

@hk21702 hk21702 commented Dec 17, 2024

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.

  • Project file structure
  • Ubuntu CLA workflow
  • PR title check
  • Jira workflow
  • README.md
  • CONTRIBUTING.md
  • Issue templates

UDENG-5667

@hk21702 hk21702 self-assigned this Dec 17, 2024
@hk21702 hk21702 changed the title [UDENG-5667] initalize and setup repository refactor(initial): [UDENG-5667] initalize and setup repository Dec 17, 2024
- 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).
Copy link
Collaborator Author

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?
Copy link
Collaborator Author

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
Copy link
Collaborator Author

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
Copy link
Collaborator Author

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.
@hk21702 hk21702 force-pushed the UDENG-5666-initalize-and-setup-repository branch from b8d8ca2 to 7f78eb3 Compare December 17, 2024 18:24
@hk21702 hk21702 marked this pull request as ready for review December 19, 2024 15:42
Copy link
Collaborator

@sharder996 sharder996 left a 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.

@hk21702
Copy link
Collaborator Author

hk21702 commented Dec 19, 2024

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?

@sharder996
Copy link
Collaborator

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 .go files and a few other files in the diff show no newline and the bottom of the file. General best practice is to have newlines at the end of files. Normally, text editors should add this automatically, but if not it will create potentially annoying diffs in the future when the next contributor adds the newlines.

Copy link
Collaborator

@Sploder12 Sploder12 left a 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

@sharder996
Copy link
Collaborator

@hk21702 There are still a bunch of file/line ending issues showing in the diff on github.

@hk21702
Copy link
Collaborator Author

hk21702 commented Dec 20, 2024

@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.

image
image

@Sploder12
Copy link
Collaborator

I think GitHub just ignores the white space at the end of files in the diff. On my local clone, the new lines exist.

No, take cmd/exposed-server/daemon/daemon.go for example. The lack of new-line shows as the red thing.
image
image

@hk21702 hk21702 requested a review from sharder996 January 6, 2025 13:49
Copy link
Collaborator

@sharder996 sharder996 left a 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!

Copy link
Collaborator

@Sploder12 Sploder12 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@hk21702 hk21702 merged commit dd0f241 into ubuntu:main Jan 9, 2025
@CarlosNihelton
Copy link
Contributor

What about that commit @Patriot7865 ?

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

Successfully merging this pull request may close these issues.

4 participants