2.1 release download in GitHub is not the same as release_2_1 branch
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- git, github
- Domain
- release
Research direction
Start by comparing the GitHub 2.1 release download with the release_2_1 branch and identify which contents differ. Trace how the release download was produced, then make the published 2.1 download match the release_2_1 branch and verify the schemas can be parsed consistently.
Written by the indexing model from the issue text.
Description
This cost me quite some time as I was trying to figure out how to parse the schemas.
- Dominant language
- No language data
- Stars
- 238
- Forks
- 67
- PR merge metrics
- No merged PRs in 30d
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.
More from buildingSMART/BCF-API
-
Difficulty 2/5 1-3 hours Newbie friendliness 48/100
buildingSMART/BCF-API#395 ·
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
buildingSMART/BCF-API#394 ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
buildingSMART/BCF-API#392 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 45/100
buildingSMART/BCF-API#390 ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
buildingSMART/BCF-API#389 · 2 comments ·
All issues in buildingSMART/BCF-API
Similar issues
-
Help-Wanted Needs-Triage Package-Request
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
microsoft/winget-pkgs#438680 ·
-
package-update
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
oSoWoSo/vOid_Community_repOsitory#148 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
-
documentation pkg infrastructure
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
epiverse-trace/epiparameter#511 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100