undefined | Better HN

0 pointsstickfigure1mo ago0 comments

That lacks imagination. There's no corporate workflow that can't ultimately translate to moving git tags.

0 comments

ragall1mo ago

Perhaps, but why should one do it when it's a bad model ? Jury because it's possible ?

jeswin1mo ago

How did you objectively decide it's a bad model?

Daviey1mo ago

Because it's more enterprise to open a Service Now ticket and have Joe from IT upload the new content using FTP.

ragall1mo ago

I subjectively did based on my experience.

Except you want to track what went to production and what didn't and for how long

Releases of a Heroku app is tracked by the platform, and both shown the the UI, in the CLI and available in the API.

Git is remarkably good at tracking history. CI systems are also great at showing history.

j / k navigate · click thread line to collapse

ragall1mo ago

Perhaps, but why should one do it when it's a bad model ? Jury because it's possible ?

jeswin1mo ago

How did you objectively decide it's a bad model?

Daviey1mo ago

Because it's more enterprise to open a Service Now ticket and have Joe from IT upload the new content using FTP.

ragall1mo ago

I subjectively did based on my experience.

Except you want to track what went to production and what didn't and for how long

Releases of a Heroku app is tracked by the platform, and both shown the the UI, in the CLI and available in the API.

Git is remarkably good at tracking history. CI systems are also great at showing history.

j / k navigate · click thread line to collapse