Improve Transparency of files included in a release

What problem are we trying to solve?

As we were troubleshooting this incident, we were slowed down by the inability to quickly identify which files were included in the recent release. These are the steps that were taken and we were unable to figure it out:

This seems to be a recurring problem during incident calls where SREs are on a call and they don't have a good idea of what was in what deploy without doing quite a bit of manual work, or asking a release manager.

1. Go to #announcements.
2. Click on the Sentry link.
3. Look at the changed files.

Purpose

The purpose of this issue is to identify a solution that will allow us to more efficiently determine what was most recently included in a release.

Should we look into a more efficient way to find the changeling for the most recent deployment. At one point, we looked through the announcement channel. I was not sure if there was a better way to do this?

Proposed Solutions

1. Can we add a compare link to #announcement similar to the Sentry one?
2. Can we figure out why Sentry didn't know about that MR - maybe I picked the wrong MR?

Please read this for context

Either way, it's quite a common theme of incident calls I've been on that we don't have a good idea of what was in what deploy without doing quite a bit of manual work, or asking a release manager.