Combine Pull Request numbers with build number

[dennisdoomen]

Up until now, we've been using some custom logic to append the build number to the version GitVersion calculates for Pull Request builds. This is to ensure that force pushes to feature branches (which I do all the time) still result in uniquely versioned NuGet packages. So, in the case of Fluent Assertions, a build for PR #2901 with build number 4081 results in 8.0.0-pr2901.4081. Since I'm going to give a talk mentioning GitVersion soon, I was wondering if this is now supported out-of-the-box.

[HHobeck]

Interesting, what version of GitVersion you are using and what workflow? Have you customized the configuration? The question is a little bit out of scope: How do you ensure the namespace and assembly integrity in you projects? Maybe you can mention the NsDepCop project in your talk.

[dennisdoomen]

Interesting, what version of GitVersion you are using and what workflow? Have you customized the configuration

We are using 6.1 (see here). And yes, we have customized the configuration. But how is that related to my question? 🤔

How do you ensure the namespace and assembly integrity in you projects? Maybe you can mention the NsDepCop project in your talk.

I never bothered to spend time on that. But that project looks quite nice.

[HHobeck]

We are using 6.1 (see here). And yes, we have customized the configuration. But how is that related to my question? 🤔

Because I want to know if you are working with a 6.x version or not. The following discussion goes in the same direction:

• Extend GitVersion to Count Builds within a Version #4272

At the moment overruling the CommitsSinceVersionSource is not possible.

[dennisdoomen]

At the moment overruling the CommitsSinceVersionSource is not possible.

Thanks for confirming. Whenever I prepare a talk, I'd like to revisit some of my assumptions.