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
Hi! I'm loving using your action, and just ran into a case where I had a file renamed and modified. I'm currently using the added_modified output, and I was puzzled that it didn't show up in that set. If the name added_modified indicates added OR modified, I'm wondering why the renamed file does not appear there? I don't think it means added and modified because it definitely triggers for files that are existing and just changed.
While I would expect all renamed files to be under renamed, this set alone doesn't give me enough information to tell me if a file is renamed and modified. For the subset of renamed files that are modified, I would think they would appear in added_modified? I'm not sure if this is a bug but please let me know if there is another way to get that list!
The text was updated successfully, but these errors were encountered:
This functionality exists in @Ana06's fork Ana06/get-changed-files. For more information, read the README of check out the commit that added the feature: 47aa8c6
Hi! I'm loving using your action, and just ran into a case where I had a file renamed and modified. I'm currently using the added_modified output, and I was puzzled that it didn't show up in that set. If the name
added_modified
indicates added OR modified, I'm wondering why the renamed file does not appear there? I don't think it means added and modified because it definitely triggers for files that are existing and just changed.While I would expect all renamed files to be under renamed, this set alone doesn't give me enough information to tell me if a file is renamed and modified. For the subset of renamed files that are modified, I would think they would appear in added_modified? I'm not sure if this is a bug but please let me know if there is another way to get that list!
The text was updated successfully, but these errors were encountered: