Skip to content
This repository has been archived by the owner on Feb 12, 2024. It is now read-only.

Configuration for labels-and-milestones sync tool #595

Closed
wants to merge 1 commit into from

Conversation

flyingzumwalt
Copy link

This adds the labels-and-milestones sync tool with configs for the go-ipfs Q4 roadmap.

I'm not convinced this is the right place for these configs.

For more info, see ipfs/team-mgmt#257

License: MIT
Signed-off-by: Matt Zumwalt <matt@databindery.com>
@daviddias
Copy link
Member

same as #596 (comment)

@flyingzumwalt
Copy link
Author

@diasdavid please download this code and run it once. That will add the
milestones to all of your remaining repos so your team can associate issues
with them. Most of the repos have already been synced but I still don't
have access to the multiformats ones.

I can follow up on figuring out where these configs should live for the
long term and how to make CI run them.
On Mon, Nov 21, 2016 at 4:58 AM David Dias notifications@github.com wrote:

Assigned #595 #595 to @flyingzumwalt
https://github.com/flyingzumwalt.


You are receiving this because you were mentioned.

Reply to this email directly, view it on GitHub
#595 (comment), or mute the
thread
https://github.com/notifications/unsubscribe-auth/AAIesgiFAzWuTaTHYOMtEmo58WgsQqibks5rAWs8gaJpZM4Ky8vf
.

@daviddias daviddias added js-ipfs-ready and removed status/in-progress In progress labels Nov 27, 2016
@daviddias daviddias added status/ready Ready to be worked and removed js-ipfs-ready labels Dec 5, 2016
@daviddias
Copy link
Member

Where is this tool living currently? Is there a repo? Is it safe to close the PR?

@daviddias
Copy link
Member

Closing this PR in favour of tracking the dev of the tool at ipfs/team-mgmt#237

@daviddias daviddias closed this Jan 9, 2017
@daviddias daviddias deleted the labels-and-milestones branch January 9, 2017 12:12
@daviddias daviddias removed the status/ready Ready to be worked label Jan 9, 2017
@flyingzumwalt
Copy link
Author

We should revisit to confirm that we still want to proceed with this approach -- it was all motivated by the pm process document, which we never ratified, instead leaving it as just a draft. I suspect that we will want to adopt a modified version of the stuff in that doc (possibly simplified) and will still have use for labels-and-milestones for as long as we use github (won't need it if/when we migrate to gitlab)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants