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

docs: update the general guidelines section #1377

Closed
wants to merge 2 commits into from

Conversation

YashPimple
Copy link
Member

Related #972
Fixes #995

Signed-off-by: Yash Pimple [email protected]

@YashPimple YashPimple requested review from a team as code owners May 5, 2023 06:53
@github-actions github-actions bot added the documentation Improvements or additions to documentation label May 5, 2023
@netlify
Copy link

netlify bot commented May 5, 2023

Deploy Preview for keptn-lifecycle-toolkit ready!

Name Link
🔨 Latest commit e518dc4
🔍 Latest deploy log https://app.netlify.com/sites/keptn-lifecycle-toolkit/deploys/6454a7e3e6a60c0008c04df2
😎 Deploy Preview https://deploy-preview-1377--keptn-lifecycle-toolkit.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site settings.

@sonarqubecloud
Copy link

sonarqubecloud bot commented May 5, 2023

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

@StackScribe
Copy link
Contributor

Nice work, @YashPimple ! I apologize for the confusion about all this so let me try to clarify.

  • The guidelines should be in the general section of the Contributing Guide rather than software because they apply to documentation as well as software
  • The guidelines themselves should then be removed from both the lifecycle-toolkit/CONTRIBUTING.md file leaving just. the link.

The concept is that having a CONTRIBUTING.md file in the root of the repo is a convention but that file has become rather difficult to read. So we move the real content to the Contributing Guide but leave links to that guide in CONTRIBUTING.md.

We did have a separate CONTRIBUTING.md file for docs but I can't find that right now. And I'm not sure whether we need it with the docs and software in the same repo. A lot of the info duplicated material/topics that were also in the main CONTRIBUTING.md file . But we do need info about how to build the docs locally, markdown lint, the structure of the doc source files, et cetera. @aepfli has been doing some work in this general area -- perhaps he can explain and give guidance.

But we do not need to solve all of that for this PR. Please do the following:

  • Move the guidelines list into the general directory
  • Remove the guidelines list from the CONTRIBUTING.md file, leaving just the link as you have it.

With that, hopefully we can get this merged and you'll be an official contributor -- congratulations!

@YashPimple
Copy link
Member Author

Thank you for the clarification, @StackScribe! I understand that the guidelines should be moved to the general section of the Contributing Guide, and removed from the lifecycle toolkit/CONTRIBUTING.md file, leaving only the link. I will make the necessary changes as requested.

Regarding the separate CONTRIBUTING.md file for docs, I will check with @aepfli for guidance on whether we need it or if the information can be consolidated into the main CONTRIBUTING.md file.
I will make the changes as requested and submit the updated PR for review.

@YashPimple
Copy link
Member Author

YashPimple commented May 6, 2023

@StackScribe I have made a New PR #1388 addressing the above comment.

@mowies
Copy link
Member

mowies commented Jun 12, 2023

Closed in favor of #1411

@mowies mowies closed this Jun 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Contributing: general guidelines
3 participants