-
Create a Branches page with the help of branches_data.json (in Backend)
-
Renovate should run on any `hotfix/*` branch, updating only patch versions of dependencies.
No auto-merge, as this will require a release.
-
Seach through all branches and carefully purge them. Some may seem obsolete but may have important topic information such as ML or CWL.
-
While pushing make sure you use, git push origin HEAD
-
Hi,
I know how to do that now, should we modify the scripts to be able to display on branches at next update ?
That would facilate interpretation for our user who do not know how to manipulate tree…
-
### Environment information
```plain text
System:
OS: Linux 5.15 Ubuntu 20.04.6 LTS (Focal Fossa)
CPU: (12) x64 12th Gen Intel(R) Core(TM) i5-1230U
Memory: 4.23 GB / 7.76 GB
Shell: /bi…
-
We could establish a convention that only branches beginning with `iss` trigger the deployment of a branch version of the site. This would avoid clutter in the branch versions directory, especially fr…
-
| | |
| --- | --- |
| Bugzilla Link | [47210](https://llvm.org/bz47210) |
| Version | trunk |
| OS | Linux |
| Reporter | LLVM Bugzilla Contributor |
| CC | @jdoerfert,@arsenm,@mike-myers-tob,@nhaeh…
-
Hello. I use this tool because the original (@semantic-release/changelog) generates the notes in the changelog.md file whenever a release is generated.
I only want to write the changelog.md file wh…
-
Updating contribution doc to include info on syncing R with GitHub branches. This will make testing easier, and will make sure the branch is synced and package is the relevant version requiring test…