(It’s weird that I need to explain this to you, but here goes)
It’s a fully supported feature according to the 1.0 docs:
The experimental feature you’re speaking of is per-branch notifications, which is not what I’m referring to.
It definitely has been working in 2.0. I was just looking to tweak our infrastructure around this feature and was surprised to not find it in the docs.
- If it is to be a supported feature, it would be great to have that noted in the Circle 2.0 docs
- If it’s not, what would you suggest to replace it - something that will be notified of a build after it’s completely finished so our infrastructure can react properly.
This seems like a non-optional feature to me.