infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Lambertus (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (INFRA-18085) Setup GitHub Mirrors with correct informations Name / Tags / URL Link etc.
Date Sat, 13 Apr 2019 15:50:00 GMT

     [ https://issues.apache.org/jira/browse/INFRA-18085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Chris Lambertus updated INFRA-18085:
------------------------------------
    Status: Waiting for user  (was: Waiting for Infra)

> Setup GitHub Mirrors with correct informations Name / Tags / URL Link etc.
> --------------------------------------------------------------------------
>
>                 Key: INFRA-18085
>                 URL: https://issues.apache.org/jira/browse/INFRA-18085
>             Project: Infrastructure
>          Issue Type: Task
>          Components: Github
>            Reporter: Karl Heinz Marbaise
>            Priority: Minor
>
> Related to INFRA-15963 (done for a very low number of repos)
> I would like to know what would be the best way to handle the change of about 100 github
repos.
> In each repo the following things needed to be done:
> * Setting the Name (like "Apache Maven EAR Plugin")
> * Setting the URL of the homepage of the appropriate project
> * Setting the tags for the plugin, component etc. (maven-plugin, maven-ear-plugin, apache-maven,
java changes for each of the plugins/components)
> I think the only solution could be a kind of scripting.
> The question is: 
> What kind of tools would be the best to make it easy for INFRA to run such "script" using
the correct permissions?
> Do you have already such kind of tools ? 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message