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.

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

feat: add 4EVERLAND to list of pinning service providers #2107

Merged
merged 1 commit into from
Jul 18, 2023

Conversation

cachalots
Copy link
Contributor

@cachalots cachalots requested a review from a team as a code owner March 15, 2023 08:55
@welcome
Copy link

welcome bot commented Mar 15, 2023

Thank you for submitting this PR!
A maintainer will be here shortly to review it.
We are super grateful, but we are also overloaded! Help us by making sure that:

  • The context for this PR is clear, with relevant discussion, decisions
    and stakeholders linked/mentioned.

  • Your contribution itself is clear (code comments, self-review for the
    rest) and in its best form. Follow the code contribution
    guidelines

    if they apply.

Getting other community members to do a review would be great help too on complex PRs (you can ask in the chats/forums). If you are unsure about something, just leave us a comment.
Next steps:

  • A maintainer will triage and assign priority to this PR, commenting on
    any missing things and potentially assigning a reviewer for high
    priority items.

  • The PR gets reviews, discussed and approvals as needed.

  • The PR is merged by maintainers when it has been approved and comments addressed.

We currently aim to provide initial feedback/triaging within two business days. Please keep an eye on any labelling actions, as these will indicate priorities and status of your contribution.
We are very grateful for your contribution!

@SgtPooki
Copy link
Member

Currently blocked by ipfs-shipyard/pinning-service-compliance#287

@cachalots cachalots temporarily deployed to Deploy March 27, 2023 17:58 — with GitHub Actions Inactive
@cachalots
Copy link
Contributor Author

Currently blocked by ipfs-shipyard/pinning-service-compliance#287

We have already cleared the obstacles, please continue.

@cachalots
Copy link
Contributor Author

@SgtPooki ipfs-shipyard/pinning-service-compliance#301 Has been merged! Let's push forward the merger of this PR.

@cachalots
Copy link
Contributor Author

@SgtPooki Hello, are there any other issues that need to be addressed in this PR?

@SgtPooki
Copy link
Member

@cachalots sorry for the delay! I'm going to look at this now!

Copy link
Member

@SgtPooki SgtPooki left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@SgtPooki SgtPooki merged commit 12a0f87 into ipfs:main Jul 18, 2023
ipfs-gui-bot pushed a commit that referenced this pull request Jul 25, 2023
## [4.1.0](v4.0.2...v4.1.0) (2023-07-25)

 CID `bafybeieqdeoqkf7xf4aozd524qncgiloh33qgr25lyzrkusbcre4c3fxay`

 ---

### Features

* add 4EVERLAND to list of pinning service providers ([#2107](#2107)) ([12a0f87](12a0f87))

### Bug Fixes

* **ci:** e2e coverage ([#2142](#2142)) ([83353e0](83353e0))
* [email protected] ([#2141](#2141)) ([670ba7c](670ba7c))

### Tests

* only repeat e2e tests on PRs ([#2124](#2124)) ([530c501](530c501))
* **storybook:** add PeerBandwidthTable.stories.js ([#2095](#2095)) ([c969c5e](c969c5e))

### Trivial Changes

* Pull transifex translations ([#2137](#2137)) ([2284453](2284453))
* Pull transifex translations ([#2140](#2140)) ([95d468b](95d468b))
@ipfs-gui-bot
Copy link
Collaborator

🎉 This PR is included in version 4.1.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

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

Successfully merging this pull request may close these issues.

3 participants