You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@devlake.apache.org by "Feggah (via GitHub)" <gi...@apache.org> on 2023/09/21 19:56:09 UTC
[GitHub] [incubator-devlake] Feggah commented on issue #5178: [Feature][GitHub plugin] Support transformations from GitHub Environments
Feggah commented on issue #5178:
URL: https://github.com/apache/incubator-devlake/issues/5178#issuecomment-1730209461
Can't help much any longer by giving real-life examples @Startrekzky, I'm not in the same company that I was before.
But our use case was simple: we used environments to apply specific policies to it. For example, for production environments, we had a policy that two people had to approve before the deployment job was executed.
For DevLake specifically, using GitHub Environments would be more reliable than the job name, because we had control over the GitHub Environments and it had a pattern across the company, but for pipeline/job names, each repository had its own different pattern.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@devlake.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org