You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@beam.apache.org by "Colm O hEigeartaigh (JIRA)" <ji...@apache.org> on 2018/03/14 11:30:00 UTC

[jira] [Closed] (BEAM-3575) Update contribution guidelines to add the option of cloning from a fork

     [ https://issues.apache.org/jira/browse/BEAM-3575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Colm O hEigeartaigh closed BEAM-3575.
-------------------------------------

> Update contribution guidelines to add the option of cloning from a fork
> -----------------------------------------------------------------------
>
>                 Key: BEAM-3575
>                 URL: https://issues.apache.org/jira/browse/BEAM-3575
>             Project: Beam
>          Issue Type: Improvement
>          Components: website
>            Reporter: Colm O hEigeartaigh
>            Assignee: Colm O hEigeartaigh
>            Priority: Major
>             Fix For: 2.4.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> The contribution guidelines currently show how to clone Beam from the GitHub read-only mirror and then to add the user's own GitHub repo as a remote. However, it's also possible (and common) to fork the repo manually and then to clone the forked repository and work with the original repo as a remote. We should update the contribution guidelines to show this as an alternative.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)