You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment users can close [track/]risk[/branch] only.
However one channel/track usually has several bases, some might be deprecated or just garbage.
It is a feature request to close the specific base only.
The base 20.04 is not updated for many years and was the earlier experiments, garbage at the moment.
We should like to hide/remove/close it to avoid users confusing.
Unfortunately, it is not currently possible, we can close the whole track/risk[/branch] only.
Q2: BTW, can I close the whole track latest and then push base 22.04 only (to reopen latest).
Will 20.04 re-appear in this case?
Tnx!
Why it needs to get done
See the example above: to clean early experimental bases in the actively supported track.
The text was updated successfully, but these errors were encountered:
What needs to get done
Hi,
At the moment users can close [track/]risk[/branch] only.
However one channel/track usually has several bases, some might be deprecated or just garbage.
It is a feature request to close the specific base only.
Example, see the charm https://charmhub.io/data-platform-libs :
The base 20.04 is not updated for many years and was the earlier experiments, garbage at the moment.
We should like to hide/remove/close it to avoid users confusing.
Unfortunately, it is not currently possible, we can close the whole track/risk[/branch] only.
Q2: BTW, can I close the whole track
latest
and then push base 22.04 only (to reopenlatest
).Will 20.04 re-appear in this case?
Tnx!
Why it needs to get done
See the example above: to clean early experimental bases in the actively supported track.
The text was updated successfully, but these errors were encountered: