I am learning Mercurial in a corporate environment. The plan is to use central repositories hosted on a web server (IIS), which developers will use if they tested the changes locally or within their teams.
I have IIS configured to authenticate users in Active Directory, but there seems to be a hole in it, while I can ensure who can click, I cannot ensure that they sign their changes as they do.
For example, in the base “commit” scenario:
- user writes to local repository
- user transfers their changes to the central repository
In step 1, the user provides the username (via their .hgrc file or something else) to their local repository, but there really is no way to guarantee that this is their "real" username.
In step 2, the user must provide their "real" credentials for IIS so that they can be clicked, but their changes will be displayed in the history with any username that they provided in step 1. It seems that if the bean used "alice", like his username for step 1, he could make sure Alice got the blame for any of her mistakes.
Is there any way to make sure that these usernames match at the time of pushing (via hooks or something else)? Or, alternatively, in some other way to provide a sufficient level of confidence in the change for a long time?
: , , , ; , , . , , , , , .
GpgExtension , , .