When adding or removing a team member, the repository of the changed team should get updated accordingly. The old members should lose access and the new ones should get it. Currently, Artemis does not forward such changes to the repository. These changes also don't get respected in later operations (e.g. locking the repository after the deadline). For some reason, Artemis still uses the initial list of team members for this operation.
To Reproduce
You need a Programming Exercise with Teams
Create teams
Start the exercise
Change the team
The changes should be forwarded, but they are not.
Note: This issue was experienced on the now-discontinued Bitbucket system. We need to re-test if this is also an issue on other external VCS systems like GitLab.
Describe the bug
When adding or removing a team member, the repository of the changed team should get updated accordingly. The old members should lose access and the new ones should get it. Currently, Artemis does not forward such changes to the repository. These changes also don't get respected in later operations (e.g. locking the repository after the deadline). For some reason, Artemis still uses the initial list of team members for this operation.
To Reproduce
Expected behavior
Forward the changes.
Screenshots
No response
What browsers are you seeing the problem on?
Other (specify in "Additional context")
Additional context
No response
Relevant log output
No response