web3privacy / web3privacy/explorer-data
Editor updates go through multiple PRs instead of in a single PR
Open
Nobody has claimed this yet.
bug
- Dominant language
- JavaScript
- Stars
- 35
- Forks
- 63
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 7
Description
This makes it prone to errors from maintainers who're merging requests, then leading to future errors on tests runs.
Would be great if someone could look into this and fix the Github Editor flow
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the attached screenshot and reproducing the GitHub Editor flow that creates multiple pull requests. Trace where editor updates are split and run the affected test suite to observe the reported errors. Done means an editor update is delivered through a single pull request and the tests pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, javascript
- Domain
- developer-experience
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100