#1: repo init - common AbsaOSS repo files, utils, configuration, CI for Sbt-based libraries we use#3
#1: repo init - common AbsaOSS repo files, utils, configuration, CI for Sbt-based libraries we use#3
Conversation
…or Sbt-based libraries we use
JaCoCo 'mag' module code coverage report - scala 2.12.21
|
…ource files not yet committed
…inst 1 source file
.github/ISSUE_TEMPLATE/bug_report.md
Outdated
| @@ -0,0 +1,29 @@ | |||
| --- | |||
There was a problem hiding this comment.
YAML templates are the new standard for repos instead of markdown. I bet @HuvarVer could get you some nice ones.
There was a problem hiding this comment.
Ok, bring it on. Thanks! In terms of these templates I just copy pasted what we had in other OSS repos
There was a problem hiding this comment.
Since I was doing also a repo init by the end of last week, you can look into the .github/ folder inside our AguaSec Scan Results to see all the templates, PR template: https://github.com/AbsaOSS/aquasec-scan-results/tree/master/.github
There was a problem hiding this comment.
@lsulak You can find templates also here in our organizational repository
https://github.com/absa-group/cps-organizational/tree/master/.github/ISSUE_TEMPLATE
There was a problem hiding this comment.
Ok thanks, will adapt in the next commit
| steps: | ||
| - uses: actions/setup-python@83679a892e2d95755f2dac6acb0bfd1e9ac5d548 | ||
| with: | ||
| python-version: '3.11' |
There was a problem hiding this comment.
Please for this workflow and release_draft.yml look inside the link, I send in the other comment. They might be the newest ones. For example we are aiming to run our Python workflows with 3.13 even better 3.14. Not sure, if it would contain any other differences.
There was a problem hiding this comment.
Ok, thanks, will definitely check
…I files provided by our internal QA team
4 participants
Closes #1
Release Notes