Currently, it creates contributions for any meetings in the entire Zoom account that the JWT app is registered for, resulting in e.g. 5apps meetings being counted as Kosmos ones.
Currently, it creates contributions for *any* meetings in the entire Zoom account that the JWT app is registered for, resulting in e.g. 5apps meetings being counted as Kosmos ones.
But the implementation should probably be an array/list, so that we can have more than one room. Not very important compared to counting wrong ones though.
Yup: https://wiki.kosmos.org/Main_Page#Weekly_conference_calls
But the implementation should probably be an array/list, so that we can have more than one room. Not very important compared to counting wrong ones though.
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.
Currently, it creates contributions for any meetings in the entire Zoom account that the JWT app is registered for, resulting in e.g. 5apps meetings being counted as Kosmos ones.
hmm.... does it have a fixed ID? if so it should be easy.
Yup: https://wiki.kosmos.org/Main_Page#Weekly_conference_calls
But the implementation should probably be an array/list, so that we can have more than one room. Not very important compared to counting wrong ones though.