Dev branche

Thanks for the ticket.

There should be a DEV branch now. Sorry, I come from pure Github/OS world and haven't worked with Drupal OS in like 10-12 years, so I have to read up on best practices.

Awesome and welcome back :)

I don't see it yet but maybe there's a delay.

Hi Marcus,

Seems like maybe something is not set up right, if I try to download or clone from the repository, I am redirected to the project page.

https://git.drupalcode.org/project/ai_interpolator/-/tree/dev?ref_type=h...

Composer is also not finding it and it's not at the "all releases" page, but then again I don't know if there is a delay in that.

When I was creating branches for aidev module, I deleted "main" branch and created single "1.0.x" development branch (after checking out examples from other modules).

Now, comparing ai_interpolator and aidev we see that:

• AI intepolator has two branches "main" and "dev" https://git.drupalcode.org/project/ai_interpolator/-/branches
• versus aidev module has single "1.0.x" branch https://git.drupalcode.org/project/aidev/-/branches

I think you have to create "1.0.x" branch, and then go to another place (instructions below) to make a development release:

1. Go to project page https://www.drupal.org/project/ai_interpolator →
2. Click "Edit"
3. Click "Releases"
4. Click "Add new release"
5. Next, I hope it will let you to create a development release from "1.0.x" branch.

This way, people will be able to install development release on their sites.

Documentation → says, that:

Git’s default master branch should be avoided and no downloadable releases can be tied to that branch. Master branch cleanup information here → .

also

Although master branches are commonly used in the Git world, the Drupal community uses [...] semantic versioning branches (e.g., 1.0.x) instead

But there were recent changes for Drupal core :)

Drupal core is moving towards using a main branch.

https://www.drupal.org/about/core/blog/new-drupal-core-branching-scheme-... →

@mindaugasd - Thank you, I hope that did the trick. There is a dev release now here: https://www.drupal.org/project/ai_interpolator/releases/1.0.x-dev → and there is a 1.0.x branch that I made the main repo now.

@AlfTheCat - Hopefully it works now.

I guess I will do Git Flow (what I'm used to) on this module, and Github Flow on the plugin modules, since they are less complex. Or switch to Git Flow whenever there are more maintainers working on it.

So from now on (for my own documentation):
1. Smaller bugs or changes are pushed directly to the 1.0.x branch.
2. Larger bugs, features, tasks are pushed to a feature branch and when ready its merged with 1.0.x branch.
3. Whenever a new release is made, they will be merged into Main with squash strategy.

Looks good

Great work, working well now!

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