The following 100+ feature branches are related to closed bugs. I think these
can safely be deleted (the branch names aren’t exact but pretty close):
GEODE-1017: "Closed"
GEODE-1040: "Closed"
GEODE-1050: "Closed"
GEODE-1056: "Closed"
GEODE-1072: "Closed"
GEODE-1096: "Closed"
GEODE-1109: "Closed
Last chance to comment: I’ll be cleaning up these branches over the next few
days.
Anthony
> On Feb 27, 2017, at 8:58 AM, Dan Smith wrote:
>
> +1
>
> -Dan
>
> On Fri, Feb 24, 2017 at 10:35 PM, Anthony Baker wrote:
>
>>
>> The following 100+ feature branches are related to closed bugs. I
> On Mar 6, 2017, at 7:46 AM, Anthony Baker wrote:
>
> Last chance to comment: I’ll be cleaning up these branches over the next few
> days.
>
> Anthony
I’ve listed the remaining branches below. If you know that a branch is no
longer relevant (e.g. spotlessPlugin) feel free to remove it wit
I believe there must be some permission regarding "delete branch" that I
don't have. I did the following and the command returns saying the branch
is deleted, but the branch is STILL there.
$ git push origin --delete cluster-config
To https://git-wip-us.apache.org/repos/asf/geode.git
- [deleted]
Hi
I was wondering if we should clean up the feature branches related to closed or
resolved GEODE tickets in the origin repository. Below are the listed tickets
and associated branch.
Regards
Nabarun Nag
Branch Name
Ticket
Status
Committers [merged to develop]
origin/feature/GEODE-11
GEODE-1
+1
-Dan
On Fri, Feb 24, 2017 at 10:35 PM, Anthony Baker wrote:
>
> The following 100+ feature branches are related to closed bugs. I think
> these can safely be deleted (the branch names aren’t exact but pretty
> close):
>
> GEODE-1017: "Closed"
> GEODE-1040: "Closed"
> GEODE-1050: "Closed"
>
Along those same lines it would be really nice if people would use their own
forks for feature branches, then we wouldn't have this mess at all.
Sent from my iPhone
> On Aug 2, 2017, at 9:44 PM, Nabarun Nag wrote:
>
>
> Hi
> I was wondering if we should clean up the feature branches related
+1 to using your own fork for feature work
On Wed, Aug 2, 2017 at 10:58 PM, Jacob Barrett wrote:
> Along those same lines it would be really nice if people would use their
> own forks for feature branches, then we wouldn't have this mess at all.
>
> Sent from my iPhone
>
> > On Aug 2, 2017, at 9
+1 I did this awhile back. Once you’ve finished work on a feature branch
please remove it.
https://stackoverflow.com/questions/2003505/how-do-i-delete-a-git-branch-both-locally-and-remotely
Anthony
> On Aug 2, 2017, at 9:54 PM, Nabarun Nag wrote:
>
> Branch Name
> Ticket
> Status
> Committe
I am not sure why I have so many branches there. I don't remember I created
them. But this is what I get when I tried to delete one of them:
*$* git fetch origin
*$* git push origin --delete feature/GEODE-2632-6
error: unable to delete 'feature/GEODE-2632-6': remote ref does not exist
error:
On Thu, Aug 3, 2017 at 1:41 PM, Jinmei Liao wrote:
> I am not sure why I have so many branches there. I don't remember I created
> them. But this is what I get when I tried to delete one of them:
>
> *$* git fetch origin
>
> *$* git push origin --delete feature/GEODE-2632-6
>
> error: unable to
11 matches
Mail list logo