This repository has been archived by the owner on Aug 29, 2023. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
deploy JS unified CI script #274
deploy JS unified CI script #274
Changes from all commits
45b1e74
cf9f8c1
5cec3f5
f4d2f75
c2edd4a
1dcf962
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
vasco-santos/is-loopback-addr should also be in here but it's primary branch is called
main
and notmaster
so I guess #262 needs merging first?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note that these repos will need to grant permissions to the web3-bot.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, we don't have to wait for #262 because
$default-branch
string is already replaced in our templated with a name of the default branch. #262 only generalises the templating approach.As for more repos, how about we start with the original 4 to make sure the setup works as expected first? @achingbrain Could you check if
web3-bot
is allowed to write to ipfs/js-blockstore-core#14? I don't have access to settings in that repo.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Aha, gotcha.
I've added
web3-bot
to blockstore-core and the stewards team, @alanshaw is doing his various it-* repos.Happy to merge this without the extra repos - since the bot is gaining perms we can add them later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is someone monitoring the
web3-bot
inbox for repo invites? They have to be manually approved byweb3-bot
if you're not adding it to a repo from an org it's already a member of.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This action doesn't have to live in the
aegir
repo - when we're happy with the workflow it could be moved here.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We could also make a separate repo for it if we want to put it on the marketplace - similarly to what we did here https://github.com/protocol/cache-go-action. For now though, we can leave it in
ipfs/aegir
.