-
Notifications
You must be signed in to change notification settings - Fork 165
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create ramp chart(s) for "virtual authors" #1082
Comments
Prof @damithc, @eugenepeh , may I confirm if we can create a single ramp chart that captures the work attributed to all virtual authors (as opposed to 1 ramp chart per each virtual author) ? This decision will influence the implementation for the bugfix in #1067 My view is that creating a single ramp chart for all virtual authors will be simpler. |
Sure. Go ahead. |
I would prefer not because that is sort of making If it would a lot more to implement that change, then its an indication that there's a problem in the underlying structure that should also be fixed. |
@eugenepeh, ok, I will implement the bugfix in #1067, with the view that our goal is to have separate ramp charts for virtual authors. I'll discuss with the team in the event that major architecture changes are needed |
After #823 is fixed, users will be able to disown code by using author tags like
@@author some-randomuser
, wheresome-randomuser
is not the git authorname of any author in the AuthorConfiguration.As discussed in issue 1022, we can add ramp chart(s) for authors like
some-randomuser
, so that users can easily access all code that has been disowned.This will also benefit users who meant to claim certain code blocks but made typos in the author tags.
Note: this issue should probably be tackled after #823 is fixed.
The text was updated successfully, but these errors were encountered: