Eeshaan Sawant
Eeshaan Sawant
@shivansh-gohem, why dont you try contributing to the blog before you close this PR? This way, you will know exactly what to put in into this PR 👀 I dont...
@shivansh-gohem, I cant see you on the slack channel yet. 👀 And I can see from your other PRs that you were successful in setting up a local build of...
@khanhtc1202 I think at this point let us not focus on broken links. We will fix all of them once we have more clarity on v1 docs.
@khanhtc1202, please review. 🙌
@khanhtc1202 @t-kikuc can you guys help me label these issues appropriately and also maybe make these two issues, this and #6124 type:**EPIC**? We can then link multiple small Issues/PRs to...
Hey @shivansh-gohem. Thanks for this! Quick question, did you try to deploy this example using PipeCD? Maybe using a local build?
> Hi @eeshaanSA! Good news - I successfully tested this example with a local PipeCD v1 setup: > > **Testing Environment:** > > * PipeCD v1.0.0-alpha1 control plane > *...
@shivansh-gohem https://github.com/pipe-cd/pipecd/pull/6353#issuecomment-3569971432
Hey @shivansh-gohem, As mentioned, please take a look at my comment in the other PR that you have opened. We appreciate the use of AI for contributions, but we cannot...
To get us started, here is what I propose: the current **Contributor Guide** can be renamed to simply **Contribute**, making it inline with other CNCF project styles. ### Suggested Structure...