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
{{ message }}
Repository navigation
[BUG]: The github_team data source repositories_detailed does not directly correlate repo name with role #2496
I'd expect to be able to use a github_team data source to lookup repositories and the associated permission via the repositories_detailed attribute.
Actual Behavior
I either need to trust the the indexed in repositories_detailed & repositories match and do the custom lookup code to merge these or I need to use an additional data source to lookup the repositories by name from repositories to get the ID and then do the custom lookup code to merge these.
👋 Hey Friends, this issue has been automatically marked as stale because it has no recent activity. It will be closed if no further activity occurs. Please add the Status: Pinned label if you feel that this issue needs to remain open/active. Thank you for your contributions and help in keeping things tidy!
This issue isn't stale! IMHO using a stale bot for a repository that hasn't had any meaningful interactions from the maintainers for almost a year is user hostile.
Activity
stevehipwell commentedon Dec 4, 2024
The code to fix this is currently in #2476 but I'm planning on opening a seperate PR for this change before that gets merged.
github-actions commentedon Sep 1, 2025
👋 Hey Friends, this issue has been automatically marked as
stalebecause it has no recent activity. It will be closed if no further activity occurs. Please add theStatus: Pinnedlabel if you feel that this issue needs to remain open/active. Thank you for your contributions and help in keeping things tidy!stevehipwell commentedon Sep 1, 2025
This issue isn't stale! IMHO using a stale bot for a repository that hasn't had any meaningful interactions from the maintainers for almost a year is user hostile.