-
Notifications
You must be signed in to change notification settings - Fork 5.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Synchronize upstream telegraf (test) #11436
Synchronize upstream telegraf (test) #11436
Conversation
A10 sflow goroutines
Thanks so much for the pull request! |
Thanks so much for the pull request! |
Thanks so much for the pull request! |
@jotavalenciano hello, are you trying to update your forked Telegraf repository? Making a pull request isn't required, I found this stack overflow response helpful that guides you how to sync your forked repo: https://stackoverflow.com/questions/7244321/how-do-i-update-or-sync-a-forked-repository-on-github |
Thanks so much for the pull request! |
Thanks so much for the pull request! |
Thanks so much for the pull request! |
Thanks so much for the pull request! |
Hello @sspaink/ Thank you for the info. Yes, I'm trying to update our forked repository, but I'm having a lot of errors in the PR checks because there are some plugins which are out of date with the checks. I wanted to create the PR compared with upstream to verify the errors which are only related to our plugin. I will close the PR once I'm done |
Thanks so much for the pull request! |
Hi @jotavalenciano. When someone creates a PR, the maintainer team is notified. When you use a PR to compare your fork with upstream it takes some of our attention and time. There are other ways to compare your fork with upstream than actually creating a PR. Please don't click the "create pull request" button unless you have a change you want us to merge. Thanks! |
Ohh. I'm new at github. I didn't know that happens also when there is a Draft. It won't happen again. I'm sorry. |
Required for all PRs:
resolves #