top | item 46985127 (no title) stickfigure | 18 days ago That lacks imagination. There's no corporate workflow that can't ultimately translate to moving git tags. discuss order hn newest ragall|18 days ago Perhaps, but why should one do it when it's a bad model ? Jury because it's possible ? jeswin|18 days ago How did you objectively decide it's a bad model? load replies (2) Bombthecat|18 days ago Except you want to track what went to production and what didn't and for how long jononor|17 days ago Releases of a Heroku app is tracked by the platform, and both shown the the UI, in the CLI and available in the API. stickfigure|17 days ago Git is remarkably good at tracking history. CI systems are also great at showing history.
ragall|18 days ago Perhaps, but why should one do it when it's a bad model ? Jury because it's possible ? jeswin|18 days ago How did you objectively decide it's a bad model? load replies (2)
Bombthecat|18 days ago Except you want to track what went to production and what didn't and for how long jononor|17 days ago Releases of a Heroku app is tracked by the platform, and both shown the the UI, in the CLI and available in the API. stickfigure|17 days ago Git is remarkably good at tracking history. CI systems are also great at showing history.
jononor|17 days ago Releases of a Heroku app is tracked by the platform, and both shown the the UI, in the CLI and available in the API.
stickfigure|17 days ago Git is remarkably good at tracking history. CI systems are also great at showing history.
ragall|18 days ago
jeswin|18 days ago
Bombthecat|18 days ago
jononor|17 days ago
stickfigure|17 days ago