Skip to content

docs: resolve #8118 by updating contributing guidelines - #8960

Open
Mallikarjunadevops wants to merge 1 commit into
jenkins-x:mainfrom
Mallikarjunadevops:fix/issue-8118-contribution-docs
Open

docs: resolve #8118 by updating contributing guidelines#8960
Mallikarjunadevops wants to merge 1 commit into
jenkins-x:mainfrom
Mallikarjunadevops:fix/issue-8118-contribution-docs

Conversation

@Mallikarjunadevops

Copy link
Copy Markdown

Fixes #8118

Description

This pull request adds documentation updates that directly address the community feature request.

  • Moved the Linting instructions strictly before the Build Your Changes section so new contributors run linting checks ahead of time.
  • Added a note instructing contributors to search the main jx repository using label filters for open source contributions.

Signed-off-by: Mallikarjunadevops mallikarjunadevops@example.com
Signed-off-by: Mallikarjuna muchu.mallikarjunarpa@gmail.com

Adds a linting section and clarifies issue searching to help new contributors finding related issues using labels.

Signed-off-by: Mallikarjunadevops <mallikarjunadevops@example.com>
Signed-off-by: Mallikarjuna <muchu.mallikarjunarpa@gmail.com>
@jenkins-x-bot

Copy link
Copy Markdown
Contributor

Hi @Mallikarjunadevops. Thanks for your PR.

I'm waiting for a jenkins-x member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository.

@jenkins-x-bot

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
To complete the pull request process, please assign mentlak0
You can assign the PR to them by writing /assign @mentlak0 in a comment when ready.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Updating contribution.md file

2 participants