Konstantin Khomoutov writes:
>>4. We would like to now be able to completely eject/remove the
>> commit/patch from the staging git repository, as if it never went in,
>> as well as any other commits that might be related to it that came in
>> after that, and NOT just attempt to reverse it by
I think automation I suggest doable considering a little bit more detail
on the problem that might not be apparent in my original email.
There are 2 repositories
1. golden_repo
2. incoming_repo(think staging repo)
Every patch that will eventually go into golden_repo has to go through i.e.
On Fri, 12 Feb 2016 10:32:59 -0800 (PST)
Sarvi Shanmugham wrote:
[...]
> I am looking to implement a workflow that involves
>
>1. Developers committing a sequence of change sets, into a staging
> repository.
>
>2. Where these change sets go through some sanity testing at
> periodi
On Fri, 12 Feb 2016 10:32:59 -0800 (PST)
Sarvi Shanmugham wrote:
[...]
>4. We would like to now be able to completely eject/remove the
> commit/patch from the staging git repository, as if it never went in,
> as well as any other commits that might be related to it that came in
> after that,
Hi,
I am looking to implement a workflow that involves
1. Developers committing a sequence of change sets, into a staging
repository.
2. Where these change sets go through some sanity testing at periodic
points, say every 10 commits
3. If there is a failure, we would like to
