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
A PR that added one version (AladinDesktop-12.060-Java-17.eb)
Then, I added another (AladinDesktop-12.060-GCCcore-13.2.0-Java-17.eb). The tag bot now automatically labeled with 'update', I guess because it found the previous commit in this same branch, and consider this an 'update' of that.
Then, I removed (AladinDesktop-12.060-Java-17.eb) and the tagbot correctly labeled the PR as 'new' again.
Now, I guess this is a bit of a corner case, and I'm not sure if it is even a bug. That depends on what the design goal of the tag was, but I assume it is to check if it is new in the EasyBuild main/develop branches, not in my feature branch... I.e. I'm not sure if this is possible, but I guess it should check for prior existence in main/develop, and not the current (i.e. feature) branch.
The text was updated successfully, but these errors were encountered:
To be precise, I had:
AladinDesktop-12.060-Java-17.eb
)AladinDesktop-12.060-GCCcore-13.2.0-Java-17.eb
). The tag bot now automatically labeled with 'update', I guess because it found the previous commit in this same branch, and consider this an 'update' of that.AladinDesktop-12.060-Java-17.eb
) and the tagbot correctly labeled the PR as 'new' again.Now, I guess this is a bit of a corner case, and I'm not sure if it is even a bug. That depends on what the design goal of the tag was, but I assume it is to check if it is new in the EasyBuild main/develop branches, not in my feature branch... I.e. I'm not sure if this is possible, but I guess it should check for prior existence in main/develop, and not the current (i.e. feature) branch.
The text was updated successfully, but these errors were encountered: