Drupal Answers is a question and answer site for Drupal developers and administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a module on Drupal.org and I only have a dev branch. This is how I added my dev branch by tagging with 7.x-1.x-dev:

git commit -m 'Creating module'
git push origin 7.x-1.x
git tag 7.x-1.x-dev
git push --tags

Now I made some more changes and would like to have my dev branch updated with the latest code. I delete the tag and recreate the tag:

git tag -d 7.x-1.x-dev
git push origin :7.x-1.x-dev
git commit -m 'Adding new feature'
git push origin 7.x-1.x
git tag 7.x-1.x-dev
git push --tags

I did this and I don't see my files get updated on Drupal.org. Am I doing something wrong?

share|improve this question
    
Just to rule it out, is the double apostrophe a typo in the question? – Clive Feb 10 at 15:09
    
Yes. I fixed it. – albertski Feb 10 at 15:34
up vote 5 down vote accepted

No need to deal with tags for the dev branch. Tags are only required for stable releases.

Since you have already added your dev branch you just have to add your files, commit them and push them, like this:

  1. git add path/to/files
  2. git commit -m "Commit message"
  3. git push origin 7.x-1.x

Then you just wait for drupal.org to reroll a new dev version. It takes up to 12 hours to see a new dev version on the project page.

You should be able to see your commits though if you click the View commits link in the development sidebar block.

share|improve this answer
    
Thanks. I had a feeling I was doing it wrong. – albertski Feb 10 at 16:20

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.