You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
-34Lines changed: 0 additions & 34 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -279,37 +279,3 @@ longer configured to redirect stdout into the file.
279
279
|_TES_| tasks `executors.workdir` and `executors.env` functionality is not yet implemented. You can use them but they will have no effect |
280
280
|_TES_| tasks `volumes` and `tags` functionality is not yet implemented. You use them but they will have no effect |
281
281
|_TES_| tasks `logs.outputs` functionality is not yet implemented. However this limitation can be bypassed with tasks `outputs`|
282
-
283
-
284
-
## GIT
285
-
Current main branch is `origin/main`. This happens to be also a release branch for now. Developers should typically derive their
286
-
own feature branches such as e.g. `feature/TESP-111-task-monitoring`. This project has not yet configured any CI/CD. Releases are
287
-
done manually by creating a tag in the current release branch. There is not yet configured any issue tracking software but for
288
-
any possible future integration this project should reference commits, branches PR's etc ... with prefix `TESP-0` as a reference
289
-
to a work that has been done before such integration. Pull request should be merged using `Squash and merge` option with message format `Merge pull request #<PRnum> from <branch-name>`.
290
-
Since there is no CI/CD setup this is only opinionated view on how branching policies should work and for now everything is possible.
0 commit comments