litmuschaos / tutorials

Consists of codelabs to perform standard user flows for LitmusChaos
Apache License 2.0
5 stars 13 forks source link

Issues in Teaming in LitmusChaos Tutorial #21

Open neelanjan00 opened 2 years ago

neelanjan00 commented 2 years ago
mehabhalodiya commented 2 years ago

Hey @neelanjan00 I would like to contribute. Can you please specify where to modify in this?

neelanjan00 commented 2 years ago

@mehabhalodiya you can add the steps for accepting a team invite at this place: https://github.com/litmuschaos/tutorials/blob/9e87c961d2f482a47b5e6bd82413a3828cc518f4/tutorials-teaming-in-litmus/index.html#L112

mehabhalodiya commented 2 years ago

Oh well, thank you. One more thing: Is there any reference for adding the steps, which have been mentioned in any other file? I am a first-time contributor, so just asking :)

neelanjan00 commented 2 years ago

@mehabhalodiya you can take reference from the docs: https://docs.litmuschaos.io/docs/user-guides/accept-invite Basically, you can add the same screenshots and descriptions here as well or modify them as per your preference.

mehabhalodiya commented 2 years ago

It just came to notice that when I am clicking on Edit this page here, it shows me 404 :(

Can you please look on to that?

neelanjan00 commented 2 years ago

It just came to notice that when I am clicking on Edit this page here, it shows me 404 :(

Can you please look on to that?

@Jonsy13 v2.1 and v2.2 docs are not present in the staging branch, is this intended or this needs to be fixed?

neelanjan00 commented 2 years ago

@mehabhalodiya meanwhile if you'd like to edit that page, you can fork the litmus-docs repo, edit this file: https://github.com/litmuschaos/litmus-docs/edit/master/website/versioned_docs/version-2.2.0/user-guides/accept-invite.md and then create a PR.

Jonsy13 commented 2 years ago

@neelanjan00 Yes the branches were not synced. They have been synced now. @mehabhalodiya now you should be able to edit the page in staging. Please follow the instructions by neelanjan for the same.

thisisbillall commented 2 years ago

@neelanjan00 can i take Done button 404 issue ?

kitarp29 commented 2 years ago

Hey @neelanjan00 I have some Bandwidth I can take over this issue. Where do we want to redirect users to?

neelanjan00 commented 2 years ago

Hey @neelanjan00 I have some Bandwidth I can take over this issue. Where do we want to redirect users to?

@kitarp29 we can redirect to https://docs.litmuschaos.io or https://docs.litmuschaos.io/tutorials/

kitarp29 commented 2 years ago

Hey, @neelanjan00 all of our tutorial sites are running into this error. I was looking under Google Codelabs as to how to fix it, as these components are loaded automatically from the script. If there is some resource that you can share it would be of great help.

neelanjan00 commented 2 years ago

Hey, @neelanjan00 all of our tutorial sites are running into this error. I was looking under Google Codelabs as to how to fix it, as these components are loaded automatically from the script. If there is some resource that you can share it would be of great help.

You're right, currently there's no direct way to configure a redirect path for Codelabs. So the only viable options are to either create an issue in Codelabs and wait for a fix to be implemented or we can redeploy the tutorials to a different URL. CC: @ksatchit @uditgaurav

neelanjan00 commented 2 years ago

Hey, @neelanjan00 all of our tutorial sites are running into this error. I was looking under Google Codelabs as to how to fix it, as these components are loaded automatically from the script. If there is some resource that you can share it would be of great help.

Feel free to try to mitigate this issue in the Codelabs repo if you like @kitarp29

kitarp29 commented 2 years ago

https://github.com/googlecodelabs/tools/issues/715 I already did xD

neelanjan00 commented 2 years ago

https://github.com/googlecodelabs/tools/issues/715 I already did xD

Thank you for creating the issue. Please feel free to update here if you come up with any potential solution. Thanks for your contribution.