ladybug-tools / ladybug-tools/community
Branch- and release-driven development
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 2
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
@antoinedao
I would really like to move the Spider coding workflow over to a release- and branch-driven very git-oriented workflow. I do, however, have several stumbling blocks I have not figured out how to work-around yet.
Looking for:
- Links to scripts of every release are available
- Clicking any link will run that script in your browser
- No need for git or other tools to be used
In other words the entire history of a project - from R1 to the latest release - is always viewable and runnable by non-technical users and every release is in its own branch.
Using a CDN such as jsDelivr it is easy to link to any asset in any branch or release on GitHub.
What is not so easy is to get a link to the the multiple primary HTML files that can run and load all the relevant scripts and other assets.
Feel free to request more explanation. Any suggestions appreciated.
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 project's release branches, release scripts, and primary HTML files that load the required assets. The work is complete when each release has accessible links and its relevant scripts can be run in a browser without Git or other tools.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github
- Domain
- release, tooling, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100