Skip Menu |
 

This queue is for tickets about the Dist-Zilla-Plugin-Git-Remote-Check CPAN distribution.

Report information
The Basics
Id: 78103
Status: open
Priority: 0/
Queue: Dist-Zilla-Plugin-Git-Remote-Check

People
Owner: KENTNL [...] cpan.org
Requestors: ether [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



Subject: Should be able to check current branch, as well as branch(es) specified
Download (untitled) / with headers
text/plain 528b
Consider a release from a side branch.. which is legal if [Git::CheckFor::CorrectBranch] is not being used... [Git::Remote::Check] won't necessarily be checking the correct remote branch for unfetched changes. I'm thinking this plugin should do one of two things: - either always check the current branch (if it exists on the remote) as well as the branch(es) specified in the config, or - allow some special notation (e.g. 'checkcurrent = true') to indicate the desire to check the current branch as well as any others listed.
On 2012-06-29 05:28:28, ETHER wrote:
Show quoted text
> Consider a release from a side branch.. which is legal if
> [Git::CheckFor::CorrectBranch] is not being used... [Git::Remote::Check]
> won't necessarily be checking the correct remote branch for unfetched
> changes.
>
> I'm thinking this plugin should do one of two things:
> - either always check the current branch (if it exists on the remote) as
> well as the branch(es) specified in the config, or
> - allow some special notation (e.g. 'checkcurrent = true') to indicate
> the desire to check the current branch as well as any others listed.

Trying to implement this feature, but thoughts are cloudy and I'm not 100% sure what you're asking.

With "current" branch checking things get a little messier, ie : what if you're currently not on a branch at all, but on a detached head? Then what?

And also, the notion of it checking branches, plural, is confusing, as this plugin is only designed to handle *one* branch, and if you wanted to check multiple you'd use the plugin multiple times with different names, so to check the "Current" branch instead of a specified one will require us to try work out how local branch names map to foreign ones  ( not a trivial task ), as well as making a special case : Git::Remote::Check::Current , which would only check the current branch regardless of other plugin settings. ( Possibly incurring a duplicate check if you're on a branch that is explicitly configured via another plugin )

 

Sorry its taken me so long to respond.  =)
 


Download (untitled) / with headers
text/plain 123b
Take a look at recent work cjm has done in DZP-Git, around version 1.122770 -- you may be able to re-use quite a lot of it.
Download (untitled) / with headers
text/plain 398b
On Fri Dec 21 20:29:22 2012, ETHER wrote: Show quoted text
> Take a look at recent work cjm has done in DZP-Git, around version > 1.122770 -- you may be able to re-use quite a lot of it.
Oh yeah, this feature would be another good use for a shared git config stash - the shared config should list the 'main' and 'release' branches, and then this feature would/could check those branches as well as the current one.
Download (untitled) / with headers
text/plain 781b
resurrecting this. Show quoted text
> > With "current" branch checking things get a little messier, ie : what > if you're > currently not on a branch at all, but on a detached head? Then what?
The semantics of this module seem to be "if the remote branch has changed, abort". The next level of semantics is, if someone else has done work and I've not noticed, let me deal with that first. If HEAD points to a branch then I want to release "this branch", which can be affected by other people. If it doesn't, I want to release "this commit", which can't. So we do nothing. Show quoted text
> And also, the notion of it checking branches, plural, is confusing
Indeed. All I would want the plugin to do is ask git what remote branch I am currently tracking, fetch it, and bail if I am diverged from that branch.


This service is sponsored and maintained by Best Practical Solutions and runs on Perl.org infrastructure.

Please report any issues with rt.cpan.org to rt-cpan-admin@bestpractical.com.