How to fix a tag that got lost

If you pushed a tag to drupal.org in mid-August, 2013, and the tag never showed up when you tried creating a new release, don't fret! You can delete the tag and recreate it following the steps below (courtesy of joachim/#14):

git tag -d 6.x-2.0-alpha2
git push --delete origin 6.x-2.0-alpha2
git tag 6.x-2.0-alpha2
git push origin 6.x-2.0-alpha2

In other words:

  • delete the tag
  • push the deletion to delete it remotely
  • remake the tag
  • push the newly made tag

Original Issue

Today I was working on #1917702: D8CX: I pledge that Wysiwyg Linebreaks will have a full Drupal 8 release on the day that Drupal 8 is released., and pushed up four commits—the first three appear in the project commit log (https://drupal.org/node/1014824/commits), and the 8.x-1.x branch was created successfully.

However, the last commit (which can be seen if you use the repository viewer to view the 8.x-1.x branch) is not showing up in the commit log.

To create the commit and push it, I did the following (copied directly from bash history):

git commit -am "Issue #1917702 by geerlingguy: Port Wysiwyg Linebreaks to Drupal 8 - step 4."
git push -u origin 8.x-1.x

Additionally, the 8.x-1.5-beta1 tag I created isn't showing under the 'Create Project release' page (https://drupal.org/node/add/project-release/1014824).

To create the tag and push it, I did the following (copied directly from bash history):

git tag 8.x-1.5-beta1
git push -u origin 8.x-1.5-beta1

Please help!

Comments

ezra-g’s picture

ezra-g commented
Title: Pushed git commits and tag not appearing for Wysiwyg Linebreaks » Pushed git commits and tags are delayed, unable to create release nodes
Priority: Normal » Major

We're experiencing similar behavior. Commits are delayed in showing on drupalcode.org, and appear to be unrecognized when trying to create a new release node (eg https://drupal.org/node/add/project-release/1826306 complains that there are no valid tags or branches found, despite 7.x-3.4 being a valid tag).

ergonlogic reported the same issue in #drupal-infrastruture tonight. This my be related to #1301978: Upgrade Drush to v5 on all servers.

Escalating to "major" because of the general inability for various folks on Drupal.org to create releases.

drozas’s picture

drozas
Primary language Spanish
commented

Hello,

Just to confirm that I am experiencing the same behaviour while trying to create a dev release for an installation profile (https://drupal.org/project/qscience_profile). In my case, no commits are reflected at drupal.org at all.

sdboyer’s picture

sdboyer commented

yes, everybody's having this issue.

something someone did yesterday messed up the reposync workers, and they're now failing on everything - AND apparently eating jobs, which means those pushes have vanished into thin air. you'll have to push again, after i've fixed the problem, for the commits you made earlier to show up. it's rather a worst case scenario.

geerlingguy’s picture

geerlingguy commented

Yikes! In this case, would a simple git push -u origin [branch] do the trick after the problem is fixed, or will it require something different?

danny englander’s picture

danny englander
(he/him)
commented

Most likely related and I've run up against this too within the past 24 hours:
#2067047: Open Data project unable to create dev release
#2049753: "No valid branches or tags found" when I try to create a release, even though I have a valid tag

Also @sdboyer - wondering if you could please watch your language, it might be offensive to some users here. Thank you!

sdboyer’s picture

sdboyer commented

@geerlingguy - just your normal push will work fine.

@highrockmedia - #2049753: "No valid branches or tags found" when I try to create a release, even though I have a valid tag is gonna be something else - it's older and this issue is very recent, though the recent comments on it may be the same thing. #2067047: Open Data project unable to create dev release is probably this same problem.

and, while i appreciate you asking nicely, no, i'll not censor myself here.

sdboyer’s picture

sdboyer commented
Status: Active » Fixed

issue should now be fixed. oh, the wonders of supervisord.

danny englander’s picture

danny englander
(he/him)
commented

I can confirm this is fixed though I was not able to make a release for my alpha12 tag which had been pushed up late yesterday though I was able to make one for an alpha13 tag which I just pushed up so that works for me. Thank you!

joachim’s picture

joachim commented

> I was not able to make a release for my alpha12 tag which had been pushed up late yesterday

Same here, I can't make a release for the tag I pushed earlier today.
Can these be fixed, or do we have to treat them as lost, and skip a version number in our releases?

chx’s picture

chx commented

Joachim: "which means those pushes have vanished into thin air. you'll have to push again" -- lost.

joachim’s picture

joachim commented

But the tags appear on drupalcode.org, and when I pull from another computer, I see them too.

geerlingguy’s picture

geerlingguy commented

The tags are in git (so not really 'lost forever' from that perspective), but it looks like they've been lost to the drupal.org release system forever. I had to push another tag and simply skip the one I pushed during the downtime :(

drozas’s picture

drozas
Primary language Spanish
commented

@geerlingguy, @joachim

In my case I was creating a new branch (for a dev release), and merging it with master, deleting it remotely and create it again made the trick:

//Merge and push changes into master
git merge 7.x-1.x
git push origin master
//Delete the branch locally and remotely
git tag -d 7.x-1.x
git push origin :7.x-1.x

This might work for the tags as well.

Hope this helps!

David

joachim’s picture

joachim commented

Fixed the missing release tag!

Here are the instructions -- same principle as the branch:

- git tag -d 6.x-2.0-alpha2
- git push --delete origin 6.x-2.0-alpha2
- git tag 6.x-2.0-alpha2
- git push origin 6.x-2.0-alpha2

In other words:

- delete the tag
- push the deletion to delete it remotely
- remake the tag
- push the newly made tag

geerlingguy’s picture

geerlingguy commented

I've updated the issue summary so the instructions are at the top; thanks!

sdboyer’s picture

sdboyer commented

sorry, i wasn't watching this issue after the initial fix. the system is SUPPOSED to recover gracefully from a missing tag like this, but with the weird state in which it was dying, it clearly died in a way in which it couldn't recover effectively.

however, "lost forever" is far from true. if people are still having problems with missing tags and haven't rolled releases yet, please ping me in irc with the name of the project that's giving you trouble, and i can run a resync in 30 seconds that'll fix everything up for you.

/me wishes for more robots that could do more of this automagically...

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

Anonymous’s picture

(not verified) commented
Issue summary: View changes

Added instructions for recreating a tag.