[ 
https://issues.apache.org/jira/browse/MPIR-469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17885108#comment-17885108
 ] 

ASF GitHub Bot commented on MPIR-469:
-------------------------------------

bhamail opened a new pull request, #77:
URL: https://github.com/apache/maven-project-info-reports-plugin/pull/77

   The git documentation site has changed and the old general documentation 
page link is no longer valid. This PR updates the links to use the new general 
documentation link.
   
   [MPIR-469](https://issues.apache.org/jira/browse/MPIR-469)
   
   Following this checklist to help us incorporate your 
   contribution quickly and easily:
   
    - [x] Make sure there is a [JIRA 
issue](https://issues.apache.org/jira/browse/MPIR) filed 
          for the change (usually before you start working on it).  Trivial 
changes like typos do not 
          require a JIRA issue.  Your pull request should address just this 
issue, without 
          pulling in other changes.
          https://issues.apache.org/jira/browse/MPIR-469
    - [x] Each commit in the pull request should have a meaningful subject line 
and body.
    - [x] Format the pull request title like `[MPIR-XXX] - Fixes bug in 
ApproximateQuantiles`,
          where you replace `MPIR-XXX` with the appropriate JIRA issue. Best 
practice
          is to use the JIRA issue title in the pull request title and in the 
first line of the 
          commit message.
    - [x] Write a pull request description that is detailed enough to 
understand what the pull request does, how, and why.
    - [x] Run `mvn clean verify` to make sure basic checks pass. A more 
thorough check will 
          be performed on your pull request automatically.
    - [x] You have run the integration tests successfully (`mvn -Prun-its clean 
verify`).
   
   If your pull request is about ~20 lines of code you don't need to sign an
   [Individual Contributor License 
Agreement](https://www.apache.org/licenses/icla.pdf) if you are unsure
   please ask on the developers list.
   
   To make clear that you license your contribution under 
   the [Apache License Version 2.0, January 
2004](http://www.apache.org/licenses/LICENSE-2.0)
   you have to acknowledge this by using the following check-box.
   
    - [x] I hereby declare this contribution to be licenced under the [Apache 
License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0)
   
    - [x] In any other case, please file an [Apache Individual Contributor 
License Agreement](https://www.apache.org/licenses/icla.pdf).
   
   




> Broken link to git documentation page
> -------------------------------------
>
>                 Key: MPIR-469
>                 URL: https://issues.apache.org/jira/browse/MPIR-469
>             Project: Maven Project Info Reports Plugin
>          Issue Type: Bug
>          Components: scm
>            Reporter: Dan Rollo
>            Priority: Major
>
> The git doc site layout has changed, and the old general link in all 
> generated maven report sites is no longer valid. I've pushed a PR to change 
> the old link:
> [https://git-scm.com/documentation]
> to point to the new general git doc link:
> [https://git-scm.com/doc].
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to