This message was deleted.

It might be many things. First try refreshing the repository to make sure Rancher detected the changes…then maybe try checking the permissions on gitlab, verify the repo url, ensure you are pointing to the right branch/tag, fleet workspace mapping, or configuration…

That was what I thought as well so I updated the fleet.yaml in one of the other subfolders and Fleet pushed out the changes as expected.