Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Feat: Implement release-please (similar to ipfs and libp2p) #1978

Open
SgtPooki opened this issue Jul 18, 2022 · 1 comment
Open

Feat: Implement release-please (similar to ipfs and libp2p) #1978

SgtPooki opened this issue Jul 18, 2022 · 1 comment
Labels
kind/maintenance Work required to avoid breaking changes or harm to project's status quo P1 High: Likely tackled by core team if no one steps up topic/ci Continuous integration

Comments

@SgtPooki
Copy link
Member

SgtPooki commented Jul 18, 2022 •
edited
Loading

This is the process libp2p and jsipfs is following

See #1974 (comment) for more information.
@SgtPooki SgtPooki added the need/triage Needs initial labeling and prioritization label Jul 18, 2022
@SgtPooki SgtPooki mentioned this issue Jul 20, 2022
Closed
@lidel lidel added P1 High: Likely tackled by core team if no one steps up kind/maintenance Work required to avoid breaking changes or harm to project's status quo need/analysis Needs further analysis before proceeding need/maintainer-input Needs input from the current maintainer(s) and removed need/triage Needs initial labeling and prioritization labels Aug 8, 2022
@lidel
Copy link
Member

lidel commented Aug 8, 2022

👍 reusing flow already present in other parts of our ecosystem is a good idea.

@SgtPooki SgtPooki added topic/ci Continuous integration and removed need/maintainer-input Needs input from the current maintainer(s) need/analysis Needs further analysis before proceeding labels Dec 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/maintenance Work required to avoid breaking changes or harm to project's status quo P1 High: Likely tackled by core team if no one steps up topic/ci Continuous integration
Projects
No open projects
IPFS-GUI (PL EngRes)
Status: Planned / Backlog
Milestone
No milestone
Development

No branches or pull requests
2 participants
@lidel @SgtPooki