commit_authors
Overview
Name | commit_authors |
Type | Resource |
Id | github.migrations.commit_authors |
Fields
Name | Datatype |
---|---|
id | integer |
name | string |
email | string |
import_url | string |
remote_id | string |
remote_name | string |
url | string |
Methods
Name | Accessible by | Required Params | Description |
---|---|---|---|
get_commit_authors | SELECT | owner, repo | Each type of source control system represents authors in a different way. For example, a Git commit author has a display name and an email address, but a Subversion commit author just has a username. The GitHub Importer will make the author information valid, but the author might not be correct. For example, it will change the bare Subversion username hubot into something like hubot <hubot@12341234-abab-fefe-8787-fedcba987654> .This endpoint and the Map a commit author endpoint allow you to provide correct Git author information. Warning: Support for importing Mercurial, Subversion and Team Foundation Version Control repositories will end on October 17, 2023. For more details, see changelog. In the coming weeks, we will update these docs to reflect relevant changes to the API and will contact all integrators using the "Source imports" API. |
map_commit_author | EXEC | author_id, owner, repo | Update an author's identity for the import. Your application can continue updating authors any time before you push new commits to the repository. Warning: Support for importing Mercurial, Subversion and Team Foundation Version Control repositories will end on October 17, 2023. For more details, see changelog. In the coming weeks, we will update these docs to reflect relevant changes to the API and will contact all integrators using the "Source imports" API. |