This keeps the set_* methods as a compatibility layer, and further commits might deprecate and remove them entirely.
This is a very good idea, that way you don't have to really change too much code, yet you can use the new way if liked. Good job.
> This keeps the set_* methods as a compatibility layer, and further commits might deprecate and remove them entirely.
This is a very good idea, that way you don't have to really change too much code, yet you can use the new way if liked. Good job.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
This avoids the need for set_* methods.
Bikeshedding: https://discord.com/channels/514232441498763279/881248749849026590/881282858977738803
This keeps the set_* methods as a compatibility layer, and further commits might deprecate and remove them entirely.
Shouldn't this be called
set_thumbnail?Oh I'm dumb, thanks
This is a very good idea, that way you don't have to really change too much code, yet you can use the new way if liked. Good job.