-
Notifications
You must be signed in to change notification settings - Fork 772
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
π feat(cyctl): Show TemplateResolvedVersion on cyctl describe module
#610
Conversation
@quest-bot loot #605 |
Quest PR submitted!@ArnavK-09, you are attempting to solve the issue and loot this Quest. Will you be successful? Questions? Check out the docs. |
@petar-cvit hey, can you confirm is it what expected? |
describe module
describe module
@ArnavK-09, @s-vamshi already reached out to solve this one. When picking issues, pick the ones that nobody started working on. Also, when creating branches for new features, name them to reflect your changes. Same goes for #608. |
Oh no, i started working when it wasn't assigned to anybody, and no messages were there, I just forgot to embark it :( That means my prs are wasted? At least #608 can be accepted if it's valid and I'll change the branch name |
@petar-cvit I have changed branch name, should I file pr again if it's valid instead of #608? And could it be merged as I tried :( |
@ArnavK-09, you can close these PRs and if there are no updates from the assignees, you can reopen the PRs from the new branches. We can't merge these since others already started working on these issues. When picking issues, make sure nobody picked the issue, or if you see somebody picked the issue but there are no updates and you would like to take it, let us know, and we can figure out who to assign the issue to. |
sad |
π§ Another solver has looted Quest #605, but your efforts have not gone unnoticed. Go to https://quira.sh/quests/solver to find a new adventure π‘ Questions? Check out the docs. |
closes #605
π Description
β Checks
βΉ Additional context
is this what expected?