You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .github/workflows/devin_validate_chain_request.yml
+52-12Lines changed: 52 additions & 12 deletions
Original file line number
Diff line number
Diff line change
@@ -3,16 +3,20 @@ name: Trigger Devin for New Chain Request Validation
3
3
on:
4
4
issues:
5
5
types: [labeled]
6
+
push:
7
+
branches:
8
+
- feat/devin-new-chains-workflow
6
9
7
10
permissions:
8
11
contents: read # Required to read issue content
9
12
issues: read # Required to read issue details
10
13
11
14
jobs:
12
15
trigger-devin-chain-validation:
13
-
# This job runs only if the issue was labeled with 'type: new chain request'
16
+
# This job runs if the issue was labeled with 'type: new chain request' OR if pushed to v2.0 branch (for debugging)
14
17
if: |
15
-
github.event.label.name == 'type: new chain request'
18
+
github.event.label.name == 'type: new chain request' ||
19
+
github.event_name == 'push'
16
20
runs-on: ubuntu-latest
17
21
steps:
18
22
- name: Send Slack Notification for Chain Request Validation
@@ -22,15 +26,50 @@ jobs:
22
26
PROMPT_TEXT: |
23
27
## Context
24
28
25
-
A new issue (#${{ github.event.issue.number }}) has been labeled with "type: new chain request" in the ${{ github.repository }} repository. Your task is to validate this chain request for completeness and take appropriate action.
29
+
A new issue (#${{ github.event_name == 'push' && '6753' || github.event.issue.number }}) has been labeled with "type: new chain request" in the ${{ github.repository }} repository. Your task is to validate this chain request for completeness and take appropriate action.
${{ github.event_name == 'push' && '**Adding a new chain to the Explorer**
38
+
To get a new chain added to the Explorer, you will need to submit the following:
39
+
40
+
1. JSON-RPC spec for Wallets **(only if [one](https://docs.walletconnect.com/2.0/advanced/rpc-reference/ethereum-rpc) doesn''t already exist)**. For more information, please review the Ethereum [JSON-RPC API docs](https://ethereum.org/en/developers/docs/apis/json-rpc/).
41
+
**GitHub Link**:
42
+
2. Write a [CASA namespace spec](https://github.com/ChainAgnostic/namespaces) if not already available for this namespace.
43
+
**GitHub Link**:
44
+
3. **namespaces**:
45
+
_*known chain namespaces (e.g. eip:155 for Ethereum/EVM-based chains, solana, ...)_
46
+
4. **chains**:
47
+
_*known chains, where the primary key is a compound key composed of namespace + reference (e.g. ETH mainnet is eip155:1)._
48
+
_Please provide labels for each chain (e.g. mainnet, testnet, devnet, ...)_
49
+
5. **RPC endpoints**
50
+
_*list of common/canonical RPC endpoints for the chain(s)_
- [ ] Source of namespace (if non-EIP155) chain information (particularly chainIds): [link]
59
+
60
+
**Additional context**
61
+
Add any other context here.
62
+
63
+
**Please note:**
64
+
65
+
**Registering a chain with the Explorer does not impact or improve the ability for wallets and dapps to support your chain.** It is simply a way for users to discover wallets and dapps that support your chain by:
66
+
67
+
- Browsing the [Chains List](https://docs.walletconnect.com/advanced/multichain/chain-list)
68
+
- Filtering results programmatically via the [Explorer API](https://docs.walletconnect.com/cloud/explorer)
69
+
70
+
**It is still up to wallets and dapps to provide concrete support for your chain once it is listed as part of the Explorer.**
71
+
72
+
- [ ] I have read and understood the above clarification' || github.event.issue.body }}
34
73
35
74
## Validation Requirements
36
75
@@ -67,7 +106,7 @@ jobs:
67
106
* ${{ github.repository }} (for commenting on the issue if needed)
68
107
* reown-com/web-monorepo (for creating the PR if request is valid)
69
108
70
-
Please proceed with validating issue #${{ github.event.issue.number }} and take the appropriate action based on your assessment.
109
+
Please proceed with validating issue #${{ github.event_name == 'push' && '6753' || github.event.issue.number }} and take the appropriate action based on your assessment.
71
110
run: |
72
111
# Exit on error
73
112
set -e
@@ -100,10 +139,11 @@ jobs:
100
139
echo "Sending Slack notification for Chain Request Validation."
101
140
# Echo context information using direct GitHub context expressions for clarity and consistency.
0 commit comments