Skip to content
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

[Doc] clarify in chectl documentation when the next channel is updated #14432

Closed
themr0c opened this issue Sep 5, 2019 · 0 comments · Fixed by che-incubator/chectl#296
Closed
Labels
area/chectl Issues related to chectl, the CLI of Che area/doc Issues related to documentation kind/enhancement A feature request - must adhere to the feature request template. severity/P2 Has a minor but important impact to the usage or development of the system.

Comments

@themr0c
Copy link
Contributor

themr0c commented Sep 5, 2019

Followup of #14404

Q: The README.md for chectl is not absolutely clear: "Next is updated after each commit/Pull Request being merged in master branch." Could it be specified if it is the master branch of eclipse/che or of che-incubator/chectl?

A: It's updated after each commit inside chectl. Do you want to propose a PR to improve it ?

@themr0c themr0c added the kind/enhancement A feature request - must adhere to the feature request template. label Sep 5, 2019
@che-bot che-bot added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Sep 5, 2019
@tolusha tolusha added area/doc Issues related to documentation area/chectl Issues related to chectl, the CLI of Che team/doc severity/P2 Has a minor but important impact to the usage or development of the system. and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Sep 5, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/chectl Issues related to chectl, the CLI of Che area/doc Issues related to documentation kind/enhancement A feature request - must adhere to the feature request template. severity/P2 Has a minor but important impact to the usage or development of the system.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants