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
it is currently supported to use comments for scoping ssh keys to specific repositories which works well with deployment keys that are bound to one repository. If you follow GitHub suggestion and make use of machine users and ssh keys for organization wide access to repositories you currently cannot scope them to a pattern like [email protected]/organization/ . This would however allow to juggle with different types of ssh keys. This applies to owner based matching, too, of course.
If I understand the code right, the easiest solution might be to just allow
const parts = key.match(/\bgithub\.com[:/]([_.a-z0-9-]+\/)/i);
But I might miss a part of replacement logic here.
Best,
Caspar.
The text was updated successfully, but these errors were encountered:
Hey,
it is currently supported to use comments for scoping ssh keys to specific repositories which works well with deployment keys that are bound to one repository. If you follow GitHub suggestion and make use of machine users and ssh keys for organization wide access to repositories you currently cannot scope them to a pattern like
[email protected]/organization/
. This would however allow to juggle with different types of ssh keys. This applies to owner based matching, too, of course.If I understand the code right, the easiest solution might be to just allow
But I might miss a part of replacement logic here.
Best,
Caspar.
The text was updated successfully, but these errors were encountered: