Conversation
Member
Author
|
@chombium , @jorbaum , @chaitanyamullangi, @shrisha-c, @ssunka, @weili-broadcom Do any of you know if these bots are still used? If they are still needed, can you please log into the account and open/close a PR on any CF repo? That will mark them as active again. |
Contributor
|
@ameowlia, afaik we, the logging and metrics team, @cloudfoundry/wg-app-runtime-platform-logging-and-metrics-approvers don't have anything to do with these bots. |
Contributor
|
github releases for logging / metrics are being created as @cf-logging-metrics-bot Ex: https://github.com/cloudfoundry/loggregator-agent-release/releases/tag/v8.3.28 |
Contributor
Contributor
|
I've updated the automated dependency bumps to correctly use the @cf-logging-metrics-bot identity so future contributions should be tracked. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
According to the rules for inactivity defined in RFC-0025 following users have been deemed inactive:
@svcboteos
@cf-logging-metrics-bot
According to the revocation policy in the RFC, users have two weeks to refute this revocation. If you wish to remain a member of this working group then open up a PR to any cloudfoundry repo, this will mark the user as "active" from github's POV.