-
Notifications
You must be signed in to change notification settings - Fork 331
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
Botkube X Flux Integration blog post #1760
Comments
Thank you for sending this! I think this could be a good article for the blog, it's similar to other integration pieces we've posted before:
It's up for debate, the Should we publish this on the flux website, or as an external resource? I'm open to either possibility, I just want to highlight that we have both options now thanks to: |
Hi Kingdon, sorry for the delay. I was on PTO. Can we publish it directly on the flux website. |
We could, then we should open a PR and add the content (here in this repo) People can go and leave their comments on the doc if you have been iterating on the content there, but most people aren't going to look at it before it gets a PR draft. Also, I think you've heard we've been going through some stuff and it may be harder than usual to get eyes on a PR! But this could still work, I don't think there's any conflict with the Flux blog. I'm not sure if Flux maintainers are going to like this article for the blog, we have to ask for consensus, but if you need any help formatting it for a PR, I'm happy to do that! It looks like the copy in your doc draft is pretty solid now. |
Please refer: |
Working on a Botkube X Flux integration blog with @kingdonb after our joint office hours session.
Here's a link to the copy: https://docs.google.com/document/d/10JVI7wJgo5stM19cdO11GoxXQd7AIwY4LGjb5rJu8_Y/edit?usp=sharing
The text was updated successfully, but these errors were encountered: