[JIRA] (JENKINS-59586) Migrate GitLab API Plugin documentation from Wiki to GitHub

[o.v.nenashev@gmail.com (JIRA)]

Oleg Nenashev updated an issue

Jenkins / JENKINS-59586 Migrate GitLab API Plugin documentation from Wiki to GitHub Change By: Oleg Nenashev Component/s: gitlab-api-plugin Component/s: other Add Comment

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)

[o.v.nenashev@gmail.com (JIRA)]

Oleg Nenashev updated an issue

Jenkins / JENKINS-59586 Migrate GitLab API Plugin documentation from Wiki to GitHub Change By: Oleg Nenashev

<THIS IS A TEMPLATE ISSUE, PLEASE CLONE IT TO WORK ON A PLUGIN> We have recently introduced support of GitHub documentation on the [Jenkins Plugin Site|https://plugins.jenkins.io/]. See [https://groups.google.com/forum/#!topic/jenkinsci-dev/VSdfVMDIW-A] for the announcement.  Jenkins users seeking documentation will have a better user experience on plugins.jenkins.io than they do on wiki.jenkins.io.  At the same time, maintainers can follow the documentation-as-code approach and make documentation changes a part of pull requests. Documentation changes will be reviewed as part of pull requests and documentation contributors will be recognized, especially when combined with [Release Drafter|https://github.com/jenkinsci/.github/blob/master/.github/release-drafter.adoc]. We recommend all plugins to migrate documentation to GitHub. Steps: * Select a plugin you want to improve, clone this issue and assign the correct component ID * Review the plugin page on the Wiki and in the GitHub README. If there is missing information in the README, submit a pull request with the documentation update * Modify the documentation URL in the project file: [https://wiki.jenkins.io/display/JENKINS/Hosting+Plugins#HostingPlugins-Referencingthedocumentationpagefromtheprojectfile] Once the steps are completed and your pull request is merged by the maintainer, the GitHub landing page will be updated. The next time the plugin releases, the documentation will appear on [ https://plugins.jenkins.io/ ] .

Add Comment

[o.v.nenashev@gmail.com (JIRA)]

Oleg Nenashev created an issue

Jenkins / JENKINS-59586 Migrate GitLab API Plugin documentation from Wiki to GitHub

Issue Type: Improvement Assignee: Unassigned Components: other Created: 2019-09-30 13:31 Labels: hacktoberfest newbie-friendly Priority: Minor Reporter: Oleg Nenashev

<THIS IS A TEMPLATE ISSUE, PLEASE CLONE IT TO WORK ON A PLUGIN>

We have recently introduced support of GitHub documentation on the Jenkins Plugin Site. See https://groups.google.com/forum/#!topic/jenkinsci-dev/VSdfVMDIW-A for the announcement.  Jenkins users seeking documentation will have a better user experience on plugins.jenkins.io than they do on wiki.jenkins.io. At the same time, maintainers can follow the documentation-as-code approach and make documentation changes a part of pull requests. Documentation changes will be reviewed as part of pull requests and documentation contributors will be recognized, especially when combined with Release Drafter. We recommend all plugins to migrate documentation to GitHub. Steps: Select a plugin you want to improve, clone this issue and assign the correct component ID

Review the plugin page on the Wiki and in the GitHub README. If there is missing information in the README, submit a pull request with the documentation update

Modify the documentation URL in the project file: https://wiki.jenkins.io/display/JENKINS/Hosting+Plugins#HostingPlugins-Referencingthedocumentationpagefromtheprojectfile

Once the steps are completed and your pull request is merged by the maintainer, the GitHub landing page will be updated. The next time the plugin releases, the documentation will appear on https://plugins.jenkins.io/.

Add Comment

[fireflies.uvme@gmail.com (JIRA)]

urvah shabbir updated an issue

Jenkins / JENKINS-59586 Migrate GitLab API Plugin documentation from Wiki to GitHub

Change By: urvah shabbir We have recently introduced support of GitHub documentation on the [Jenkins Plugin Site|https://plugins.jenkins.io/]. See [https://groups.google.com/forum/#!topic/jenkinsci-dev/VSdfVMDIW-A] for the announcement.  Jenkins users seeking documentation will have a better user experience on [ plugins.jenkins.io |https://plugins.jenkins.io] than they do on [ wiki.jenkins.io |http://wiki . jenkins.io]. At the same time, maintainers can follow the documentation-as-code approach and make documentation changes a part of pull requests. Documentation changes will be reviewed as part of pull requests and documentation contributors will be recognized, especially when combined with [Release Drafter|https://github.com/jenkinsci/.github/blob/master/.github/release-drafter.adoc]. We recommend all plugins to migrate documentation to GitHub. Steps: * Select a plugin you want to improve, clone this issue and assign the correct component ID * Review the plugin page on the Wiki and in the GitHub README. If there is missing information in the README, submit a pull request with the documentation update * Modify the documentation URL in the project file: [https://wiki.jenkins.io/display/JENKINS/Hosting+Plugins#HostingPlugins-Referencingthedocumentationpagefromtheprojectfile] Once the steps are completed and your pull request is merged by the maintainer, the GitHub landing page will be updated. The next time the plugin releases, the documentation will appear on [https://plugins.jenkins.io/].

Add Comment