--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Definitely related, selenium-tests repo lost 17+ commits after such push.
With 678 members in the jenkinsci organisation, we're probably relatively exceptional; I can't imagine GitHub have much incentive to implement the type of fine-grained force-push permissions we would need.
Plus I think even with the number of members we have, git accidents are very rare, i.e. it's likely easier to fix mistakes in git, than to maintain a big set of permissions for new and existing users/repos.
BTW, out of curiosity, how did you manage to force push such a large number of repositories at the same time? :)
| Mads Nielsen Consultant Praqma A/S Tel: +45 50 98 18 09 |
g...@github.com:jenkinsci/warnings-plugin.git
! [rejected] master -> master (non-fast-forward)
Here are the repo that fail to git push as "[rejected] master -> master (non-fast-forward)"
branch-api-plugin.git
credentials-plugin.git
deployit-plugin.git
ec2-cloud-axis-plugin.git
ec2-plugin.git
email-ext-plugin.git
flexible-publish-plugin.git
gerrit-trigger-plugin.git
git-client-plugin.git
git-plugin.git
ironmq-notifier-plugin.git
jacoco-plugin.git
jobConfigHistory-plugin.git
literate-plugin.git
maven-info-plugin.git
maven-plugin.git
perforce-plugin.git
rebuild-plugin.git
sounds-plugin.git
ssh-slaves-plugin.git
subversion-plugin.git
synergy_scm-plugin.git
testlink-plugin.git
tfs-plugin.git
transifex-plugin.git
warnings-plugin.git
--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
@nicolas, I have a local clone which I last used to push a release. What do I need to do ?
Hi all,I have triggered an involuntary "forced push" last night on the list of Jenkins-CI plugins indicated below in this e-mail.My apologyI did not realise that I actually had forced push permissions and I do apologise for the inconvenience caused.The operations pushed back the all the branches to around 1 month. The history is not lost and is still on the GitHub server but on detached branches.
The solutionI can raise a request to GitHub to provide the "reflog" of those repositories and restore the branches to the point before my forced push.Alternatively the owners of those repositories can still perform a "forced push" to restore the correct position of the branches.(if you would like to do so, please write to the mailing list so that we do not overlap the recovery operations)
--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscribe@googlegroups.com.