In most products, we follow a scheduled release through production branch. However continuous merges keep happening to main branch. Sometimes, a custom critical issue may have been closed because its fix has been merged to main, but since there has been no release since its fix, the issue is not fixed in production. In such cases, whoever is doing client support, needs to know if a fix for an issue has reached production or not, and just the issue being closed is not helpful.
To fix this, the feature Add 'deployed-to-production' labels to PRs and issues deployed to production needs to be turned on for a repository. Once turned on, these set of events take place.
For each new successful deploy to production (identified by successful release events from NeetoDeploy for *-production environments), NeetoGit will track commits for the last 6 months in the current deployed tree (main/production), and identify all the PRs associated with those commits. For each of these PRs, a
deployed-to-productionlabel will be added to the PR, if it is closed and had been merged tomain.For each of the above identified PRs, associated issues are figured out. They can be identified either by the branch name (
13-fixing-the-sidebar), or by identifying keywords like closes, fixes, resolves in the PR body. For each of these associated issues, adeployed-to-productionlabel will be added to the issue if it has been closed.
This only works for apps deployed on NeetoDeploy.