Skip to content

Commit 4b0602e

Browse files
bkrembkrem
committed
debug: disable workflow
1 parent 919c9f0 commit 4b0602e

File tree

1 file changed

+163
-163
lines changed

1 file changed

+163
-163
lines changed

‎.github/workflows/devin_validate_chain_request.yml‎

Lines changed: 163 additions & 163 deletions
Original file line numberDiff line numberDiff line change
@@ -3,172 +3,172 @@ name: Trigger Devin for New Chain Request Validation
33
on:
44
issues:
55
types: [labeled]
6-
push:
7-
branches:
8-
- feat/devin-new-chains-workflow
6+
#push:
7+
#branches:
8+
# - feat/devin-new-chains-workflow
99

1010
permissions:
1111
contents: read # Required to read issue content
1212
issues: read # Required to read issue details
1313

1414
jobs:
15-
trigger-devin-chain-validation:
16-
# This job runs if the issue was labeled with 'type: new chain request' OR if pushed to v2.0 branch (for debugging)
17-
if: |
18-
github.event.label.name == 'type: new chain request' ||
19-
github.event_name == 'push'
20-
runs-on: ubuntu-latest
21-
steps:
22-
- name: Send Slack Notification for Chain Request Validation
23-
env:
24-
DEVIN_SLACK_WEBHOOK_URL: ${{ secrets.DEVIN_SLACK_WEBHOOK_URL }}
25-
DEVIN_SLACK_USER_ID: U08M9DKD4MC
26-
PROMPT_TEXT: |
27-
## Context
28-
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.
30-
31-
**Issue Details:**
32-
- **Title**: ${{ github.event_name == 'push' && '[DEBUG] debug chain request' || github.event.issue.title }}
33-
- **URL**: ${{ github.event_name == 'push' && 'https://github.com/WalletConnect/walletconnect-monorepo/issues/6753' || github.event.issue.html_url }}
34-
- **Author**: ${{ github.event_name == 'push' && 'bkrem' || github.event.issue.user.login }}
35-
36-
**Issue Body:**
37-
${{ 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)_
51-
6. **[SLIP-0044](https://github.com/satoshilabs/slips/blob/master/slip-0044.md) coin type**:
52-
_* slip44 coin type used in the namespace_
53-
54-
**References**
55-
To ensure timely processing of your request, please provide the following references:
56-
57-
- [ ] Source of RPC endpoints (e.g. RPC docs): [link]
58-
- [ ] 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 }}
73-
74-
## Validation Requirements
75-
76-
Please validate the chain request against the following complete example format:
77-
78-
**Required Elements:**
79-
1. **JSON-RPC spec for Wallets** - Only required if one doesn't already exist (link to existing spec or new spec)
80-
2. **CASA namespace spec** - GitHub link to ChainAgnostic/namespaces specification
81-
3. **namespaces** - The namespace identifier (e.g., "fil", "eip155")
82-
4. **chains** - List of chains with their CAIP-2 identifiers (e.g. "Filecoin [mainnet] fil:f")
83-
5. **RPC endpoints** - Working RPC endpoints for each chain
84-
6. **SLIP-0044 coin type** - The registered coin type number
85-
7. **References section** with:
86-
- Source of RPC endpoints (with working link)
87-
- Source of namespace chain information (with working link)
88-
8. **Confirmation checkbox** - "I have read and understood the above clarification" must be checked
89-
90-
## Your Actions
91-
92-
**If the request is INCOMPLETE or INVALID:**
93-
- Comment on the issue with a detailed summary of what is missing or incorrect
94-
- Be specific about which required elements are missing
95-
- Provide guidance on how to fix the issues
96-
- Use a helpful and constructive tone
97-
98-
**If the request is COMPLETE and VALID:**
99-
- Create a pull request in the https://github.com/reown-com/web-monorepo/ repository
100-
- Use the title: "chore: add new chains"
101-
- Use this PR as a reference for structure and format: https://github.com/reown-com/web-monorepo/pull/1923
102-
- Include all the chain information from the validated issue
103-
- Reference the original issue in the PR description
104-
105-
## Repositories Access Required
106-
* ${{ github.repository }} (for commenting on the issue if needed)
107-
* reown-com/web-monorepo (for creating the PR if request is valid)
108-
109-
Please proceed with validating issue #${{ github.event_name == 'push' && '6753' || github.event.issue.number }} and take the appropriate action based on your assessment.
110-
run: |
111-
# Exit on error
112-
set -e
113-
114-
# Check if the Slack webhook URL is provided and not empty
115-
if [ -z "${DEVIN_SLACK_WEBHOOK_URL}" ]; then
116-
echo "Error: DEVIN_SLACK_WEBHOOK_URL is not set or is empty."
117-
echo "Please ensure this secret is configured in the repository settings (Secrets and variables > Actions)."
118-
exit 1
119-
fi
120-
121-
# PROMPT_TEXT is set in the 'env' block and should be fully expanded by GitHub Actions.
122-
# Construct the final message text for Slack.
123-
MESSAGE_TEXT="<@${DEVIN_SLACK_USER_ID}> ${PROMPT_TEXT}"
124-
125-
# Create the JSON payload for Slack.
126-
# The --arg option in jq handles escaping special characters in MESSAGE_TEXT for valid JSON.
127-
echo "Attempting to create JSON payload..."
128-
JSON_PAYLOAD=$(jq -n --arg text "$MESSAGE_TEXT" '{text: $text}')
129-
JQ_EXIT_CODE=$?
130-
131-
if [ $JQ_EXIT_CODE -ne 0 ]; then
132-
echo "Error: jq command failed to create JSON payload (Exit Code: $JQ_EXIT_CODE)."
133-
# Log a snippet of the message text to aid debugging, avoiding overly long logs.
134-
echo "Original Message Text (first 200 characters):"
135-
echo "${MESSAGE_TEXT:0:200}..."
136-
exit 1
137-
fi
138-
139-
echo "Sending Slack notification for Chain Request Validation."
140-
# Echo context information using direct GitHub context expressions for clarity and consistency.
141-
echo "Repository: ${{ github.repository }}"
142-
echo "Issue Number: #${{ github.event_name == 'push' && '6753' || github.event.issue.number }}"
143-
echo "Issue Title: ${{ github.event_name == 'push' && '[DEBUG] debug chain request' || github.event.issue.title }}"
144-
echo "Issue URL: ${{ github.event_name == 'push' && 'https://github.com/WalletConnect/walletconnect-monorepo/issues/6753' || github.event.issue.html_url }}"
145-
echo "Label Added: ${{ github.event_name == 'push' && 'type: new chain request' || github.event.label.name }}"
146-
echo "Trigger Type: ${{ github.event_name }}"
147-
148-
# Send the notification to Slack using curl.
149-
# -s: silent mode (no progress meter).
150-
# -X POST: specifies the HTTP POST method.
151-
# -H "Content-Type: application/json": sets the content type header.
152-
# -d "$JSON_PAYLOAD": provides the JSON data for the request body.
153-
RESPONSE=$(curl -s -X POST \
154-
-H "Content-Type: application/json" \
155-
-d "$JSON_PAYLOAD" \
156-
"${DEVIN_SLACK_WEBHOOK_URL}")
157-
CURL_EXIT_CODE=$?
158-
159-
if [ $CURL_EXIT_CODE -ne 0 ]; then
160-
echo "Error: curl command failed to send Slack notification (Exit Code: $CURL_EXIT_CODE)."
161-
# RESPONSE might be empty or contain an error message from curl itself (e.g., if URL is malformed or network issue).
162-
echo "Curl response (if any): $RESPONSE"
163-
exit 1
164-
fi
165-
166-
# Check the content of the response from the Slack API.
167-
# A successful Slack webhook POST request typically returns the string "ok".
168-
if [ "$RESPONSE" = "ok" ]; then
169-
echo "Slack notification sent successfully."
170-
else
171-
echo "Error sending Slack notification: Slack API did not return 'ok'."
172-
echo "Response from Slack: $RESPONSE"
173-
exit 1
174-
fi
15+
# trigger-devin-chain-validation:
16+
# # This job runs if the issue was labeled with 'type: new chain request' OR if pushed to v2.0 branch (for debugging)
17+
# if: |
18+
# github.event.label.name == 'type: new chain request' ||
19+
# github.event_name == 'push'
20+
# runs-on: ubuntu-latest
21+
# steps:
22+
# - name: Send Slack Notification for Chain Request Validation
23+
# env:
24+
# DEVIN_SLACK_WEBHOOK_URL: ${{ secrets.DEVIN_SLACK_WEBHOOK_URL }}
25+
# DEVIN_SLACK_USER_ID: U08M9DKD4MC
26+
# PROMPT_TEXT: |
27+
# ## Context
28+
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.
30+
31+
# **Issue Details:**
32+
# - **Title**: ${{ github.event_name == 'push' && '[DEBUG] debug chain request' || github.event.issue.title }}
33+
# - **URL**: ${{ github.event_name == 'push' && 'https://github.com/WalletConnect/walletconnect-monorepo/issues/6753' || github.event.issue.html_url }}
34+
# - **Author**: ${{ github.event_name == 'push' && 'bkrem' || github.event.issue.user.login }}
35+
36+
# **Issue Body:**
37+
# ${{ 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) doesnt 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)_
51+
# 6. **[SLIP-0044](https://github.com/satoshilabs/slips/blob/master/slip-0044.md) coin type**:
52+
# _* slip44 coin type used in the namespace_
53+
54+
# **References**
55+
# To ensure timely processing of your request, please provide the following references:
56+
57+
# - [ ] Source of RPC endpoints (e.g. RPC docs): [link]
58+
# - [ ] 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 }}
73+
74+
# ## Validation Requirements
75+
76+
# Please validate the chain request against the following complete example format:
77+
78+
# **Required Elements:**
79+
# 1. **JSON-RPC spec for Wallets** - Only required if one doesn't already exist (link to existing spec or new spec)
80+
# 2. **CASA namespace spec** - GitHub link to ChainAgnostic/namespaces specification
81+
# 3. **namespaces** - The namespace identifier (e.g., "fil", "eip155")
82+
# 4. **chains** - List of chains with their CAIP-2 identifiers (e.g. "Filecoin [mainnet] fil:f")
83+
# 5. **RPC endpoints** - Working RPC endpoints for each chain
84+
# 6. **SLIP-0044 coin type** - The registered coin type number
85+
# 7. **References section** with:
86+
# - Source of RPC endpoints (with working link)
87+
# - Source of namespace chain information (with working link)
88+
# 8. **Confirmation checkbox** - "I have read and understood the above clarification" must be checked
89+
90+
# ## Your Actions
91+
92+
# **If the request is INCOMPLETE or INVALID:**
93+
# - Comment on the issue with a detailed summary of what is missing or incorrect
94+
# - Be specific about which required elements are missing
95+
# - Provide guidance on how to fix the issues
96+
# - Use a helpful and constructive tone
97+
98+
# **If the request is COMPLETE and VALID:**
99+
# - Create a pull request in the https://github.com/reown-com/web-monorepo/ repository
100+
# - Use the title: "chore: add new chains"
101+
# - Use this PR as a reference for structure and format: https://github.com/reown-com/web-monorepo/pull/1923
102+
# - Include all the chain information from the validated issue
103+
# - Reference the original issue in the PR description
104+
105+
# ## Repositories Access Required
106+
# * ${{ github.repository }} (for commenting on the issue if needed)
107+
# * reown-com/web-monorepo (for creating the PR if request is valid)
108+
109+
# Please proceed with validating issue #${{ github.event_name == 'push' && '6753' || github.event.issue.number }} and take the appropriate action based on your assessment.
110+
# run: |
111+
# # Exit on error
112+
# set -e
113+
114+
# # Check if the Slack webhook URL is provided and not empty
115+
# if [ -z "${DEVIN_SLACK_WEBHOOK_URL}" ]; then
116+
# echo "Error: DEVIN_SLACK_WEBHOOK_URL is not set or is empty."
117+
# echo "Please ensure this secret is configured in the repository settings (Secrets and variables > Actions)."
118+
# exit 1
119+
# fi
120+
121+
# # PROMPT_TEXT is set in the 'env' block and should be fully expanded by GitHub Actions.
122+
# # Construct the final message text for Slack.
123+
# MESSAGE_TEXT="<@${DEVIN_SLACK_USER_ID}> ${PROMPT_TEXT}"
124+
125+
# # Create the JSON payload for Slack.
126+
# # The --arg option in jq handles escaping special characters in MESSAGE_TEXT for valid JSON.
127+
# echo "Attempting to create JSON payload..."
128+
# JSON_PAYLOAD=$(jq -n --arg text "$MESSAGE_TEXT" '{text: $text}')
129+
# JQ_EXIT_CODE=$?
130+
131+
# if [ $JQ_EXIT_CODE -ne 0 ]; then
132+
# echo "Error: jq command failed to create JSON payload (Exit Code: $JQ_EXIT_CODE)."
133+
# # Log a snippet of the message text to aid debugging, avoiding overly long logs.
134+
# echo "Original Message Text (first 200 characters):"
135+
# echo "${MESSAGE_TEXT:0:200}..."
136+
# exit 1
137+
# fi
138+
139+
# echo "Sending Slack notification for Chain Request Validation."
140+
# # Echo context information using direct GitHub context expressions for clarity and consistency.
141+
# echo "Repository: ${{ github.repository }}"
142+
# echo "Issue Number: #${{ github.event_name == 'push' && '6753' || github.event.issue.number }}"
143+
# echo "Issue Title: ${{ github.event_name == 'push' && '[DEBUG] debug chain request' || github.event.issue.title }}"
144+
# echo "Issue URL: ${{ github.event_name == 'push' && 'https://github.com/WalletConnect/walletconnect-monorepo/issues/6753' || github.event.issue.html_url }}"
145+
# echo "Label Added: ${{ github.event_name == 'push' && 'type: new chain request' || github.event.label.name }}"
146+
# echo "Trigger Type: ${{ github.event_name }}"
147+
148+
# # Send the notification to Slack using curl.
149+
# # -s: silent mode (no progress meter).
150+
# # -X POST: specifies the HTTP POST method.
151+
# # -H "Content-Type: application/json": sets the content type header.
152+
# # -d "$JSON_PAYLOAD": provides the JSON data for the request body.
153+
# RESPONSE=$(curl -s -X POST \
154+
# -H "Content-Type: application/json" \
155+
# -d "$JSON_PAYLOAD" \
156+
# "${DEVIN_SLACK_WEBHOOK_URL}")
157+
# CURL_EXIT_CODE=$?
158+
159+
# if [ $CURL_EXIT_CODE -ne 0 ]; then
160+
# echo "Error: curl command failed to send Slack notification (Exit Code: $CURL_EXIT_CODE)."
161+
# # RESPONSE might be empty or contain an error message from curl itself (e.g., if URL is malformed or network issue).
162+
# echo "Curl response (if any): $RESPONSE"
163+
# exit 1
164+
# fi
165+
166+
# # Check the content of the response from the Slack API.
167+
# # A successful Slack webhook POST request typically returns the string "ok".
168+
# if [ "$RESPONSE" = "ok" ]; then
169+
# echo "Slack notification sent successfully."
170+
# else
171+
# echo "Error sending Slack notification: Slack API did not return 'ok'."
172+
# echo "Response from Slack: $RESPONSE"
173+
# exit 1
174+
# fi

0 commit comments

Comments
 (0)
⚡