Skip to main content
10 events
when toggle format what by license comment
Apr 3, 2019 at 13:42 comment added Ben Carp @RobC, yes. Obviously testing comes after the build, so "BUILD" by itself doesn't mean that I can identify it as a tested version. But I can still distinguish it from other commits, and hopefully it can bring me very close to the specific commit I am looking for.
Apr 3, 2019 at 12:50 comment added RobC So, is the BUILD - prefix a way to identify the last stable build which was tested ?
Apr 3, 2019 at 12:44 history edited Ben Carp CC BY-SA 4.0
added 3 characters in body
Apr 3, 2019 at 12:43 comment added Ben Carp @RobC, thanks! This is really helpful. The idea behind this is that the build process is separate from the Version control process. Every new version requires some QA. I try to create new features in a separate branch. But sometimes I do change the code on the master branch. Than, If an immediate patch is required to the live version, which can't wait till the next version is released. I'd like to return to the stable build, which was tested, and just change the necessary. Makes snese?
Apr 3, 2019 at 12:34 comment added RobC Out of interest, why do you not want to include the BUILD - part in the argument passed to npm run buildAndCommit ?
Apr 3, 2019 at 12:30 comment added RobC Using Powershell it's probably simpler to run npm run buildAndCommit -- "BUILD - commit for a new build", i.e. include the BUILD - prefix. However running on *nix the solution if fairly trivial.
Apr 3, 2019 at 12:24 history edited RobC CC BY-SA 4.0
Change title to better refect actual requirement; Improve formatting.
Apr 3, 2019 at 11:42 answer added RobC timeline score: 13
Apr 2, 2019 at 9:10 review Close votes
Apr 6, 2019 at 0:00
Apr 2, 2019 at 8:48 history asked Ben Carp CC BY-SA 4.0