Investigate pulling from unified and applying patch instead of pulling from try in the publication task
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
Research direction
Look at the publication task in the codebase, likely in a CI or task runner directory. Compare it to the analysis task's implementation that pulls from unified and applies a Phabricator patch. Understand the current try pull mechanism and the patch application process. Test the change by running the publication task locally or in a CI environment to ensure it works correctly and is faster.
Written by the indexing model from the issue text.
Description
The publication task is pulling from try, which can be slow.
It might make more sense to do like the analysis task: pull from unified and apply the Phabricator patch.
WDYT @cgsheeh @jcristau?
- Dominant language
- Python
- Stars
- 67
- Forks
- 53
- Avg merge
- 1d 18h
- Merged PRs (30d)
- 77
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
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.
More from mozilla/code-review
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
mozilla/code-review#3399 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
mozilla/code-review#3710 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 65/100
mozilla/code-review#3673 ·
Maintainers usually reply within 1 day
-
Investigate avoiding cloning the repo when there are no publishable issuesPossibly taken @marco-c claimed this 13 days ago. Open
Difficulty 3/5 1-2 days Newbie friendliness 65/100
mozilla/code-review#3671 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
mozilla/code-review#3666 ·
Maintainers usually reply within 1 day
All issues in mozilla/code-review
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
data-umbrella/du-event-board#225 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100