Add release tag to the CI pipeline on deploy about gpregistrypolicydsc HOT 9 CLOSED

@jcwalker how did you to the release tag, I see you solved that one for the last release? Can we automate it easily?

from gpregistrypolicydsc.

@johlju I manually created the tag. I'm not sure on the specifics on how to automate it.

from gpregistrypolicydsc.

What do you do to create the tag? What are the steps you took to create the tag?

from gpregistrypolicydsc.

I simply followed the instructions here

from gpregistrypolicydsc.

Ah cool! I think we could automate this with https://github.com/pcgeek86/PSGitHub (or some other tool), but it looks like we need to have a personal access token for an account with enough permission to create released. 🤔

from gpregistrypolicydsc.

I've been working on that ;)
You can leave this to me.

from gpregistrypolicydsc.

@gaelcolas Cool! Thank you!

from gpregistrypolicydsc.

Working on getting this repo to the new CI pipeline

from gpregistrypolicydsc.

@jcwalker from now on it will release a preview version on every merge to branch master unless you use [skip ci] in the commit title or description. If you want to release a full version you do the following https://dsccommunity.org/blog/convert-a-module-for-continuous-delivery#publish-the-next-full-version

from gpregistrypolicydsc.