I have a pipeline that builds a JavaScript project and then updates a package.json file with the new version after a successful build and pushes it back to git.
However, the package.json is _also_ used to hold the versions of other dependencies. So if I make a change that is just updating project dependencies, it will not trigger a build. So two questions: 1) Is there a workaround for this problem that anyone has figured out? 2) Is there a way to blacklist anything other than just the files changed? We could use any of the following to determine that we dont want to run an automatic build: - git commit author - git commit message Thanks, Paul -- You received this message because you are subscribed to the Google Groups "go-cd" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
