ALBERTIN TIMOTHEE p1514771 writes:
+This workflow is commonly used on different platforms like BitBucket,
+GitHub or GitLab which provide a dedicated mechanism for requesting
merges.
>>>
>>> As a user, I find it terribly frustrating when
ALBERTIN TIMOTHEE p1514771 writes:
>>> +Example with master as :
>>> +===
>>> +* `git config branch.master.remote upstream`
>>> +* `git config branch.master.pushRemote origin`
>>> +===
>
>>origin
>>> +This workflow is commonly used on different platforms like BitBucket,
>>> +GitHub or GitLab which provide a dedicated mechanism for requesting merges.
>>
>> As a user, I find it terribly frustrating when reading documentation
>> telling me that "there's a dedicated mechanism" for something
>> +
>> +
>> +-- -
>> +| UPSTREAM | maintainer | PUBLISH |
>> +||- - - - - - - -| |
>> +-- <- -
>> + \
Matthieu Moy writes:
> I don't think you should talk about "Git contributors", which can be
> read as "contributors to the git.git codebase". "Git users" would make
> more sense, or perhaps you meant "contributors to Git projects". But
> actually, I don't think this
"BENSOUSSAN--BOHM DANIEL p1507430"
wrote:
> Added a new file about triangular workflow for a clearer organization.
"for a clearer organization" is an explanation of why you are doing
things this way compared to your previous email.
But this is the
6 matches
Mail list logo