Create extension to deal with WordPress contributions #102
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…pers without access to the repository
…r errors in the regex
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I'm not sure if it is worth adding this to the main repository since it is specific to WordPress but, as suggested by @andygrunwald in this comment #98 (comment), I created an extension to deal with WordPress contributions.
WordPress identifies code contributions made by developers without access to the repository with a tag "props" followed by the user name on the commit message. This extension get the contributors names from the commit messages and populate a new column in the table scmlog called wordpress_author_id.
I'm not a Python developer and I'm not familiar with CVSAnalY code so I'm sure there is room for improvement :)