Profile updates are near-live at the moment. If I make a commit on Project A it will move to the front of the list as the most recently updated.
Imagine a situation where I am supposed to work on that boring client contract and some other exciting lot of work pops up. The client may actually see that I've been committing to some other projects and start asking questions.
We need to introduce a delay in the profile updates, say once a week or even once a month.
That should be done on the server because the reports should be submitted at the time of the commit. If they are not, there is a risk that there will be no new commits and no data submitted unless run manually.
So, we can have a config param that updates the profile once in a long while using all those earlier submitted reports. It would be pretty hard to tell which lot of work was done when.
Someone working for an evil corporate that prohibits any non-work related coding or claims ownership over such may still use it as a signal.
Profile updates are near-live at the moment. If I make a commit on Project A it will move to the front of the list as the most recently updated.
Imagine a situation where I am supposed to work on that boring client contract and some other exciting lot of work pops up. The client may actually see that I've been committing to some other projects and start asking questions.
We need to introduce a delay in the profile updates, say once a week or even once a month.
That should be done on the server because the reports should be submitted at the time of the commit. If they are not, there is a risk that there will be no new commits and no data submitted unless run manually.
So, we can have a config param that updates the profile once in a long while using all those earlier submitted reports. It would be pretty hard to tell which lot of work was done when.
Someone working for an evil corporate that prohibits any non-work related coding or claims ownership over such may still use it as a signal.