Dhaval D
Dhaval D
@nynymike yes, this is needed. My suggestion on implementation would be to have clean install by default, and have a switch or flag in case if dev-tooling is required. Something...
@shmorri Right. And I am not sure if this is needed now or not in presence of [jans.io/docs](jans.io/docs). Intention behind this page was that it provides a TOC for people...
@shmorri - I have added a commit that adds `cloud-native` tag to the documents - Should `admin/reference/kubernetes` change to `admin/reference/cloud-native` as well?
+1. This feature would be **_useful_** to us too!! Path adds context to the search results, and that can help users decide which of the search result is the best...
Partially achieved. This has been taken care by having Sonar integration with PRs. PRs can only merge after it passes quality gate. What is remaining is to triage all backlog...
Successfully integrated code coverage for fork of jans-auth-server with codacy. Now Codacy is reporting code coverage.
After integrating code coverage, when I looked at Codacy code analysis and coverage reports I found them lacking in few key aspects. Few of them are as below: - Doesn't...
Post monorepo move: Plan is to move away from Jenkins CI-CD and use GH actions. We need to be able to run tests and report code coverage to sonar for...
Hi @yurem, will this have any updates to be made to user documentation?
@shmorri @moabu This is an issue created long back. Are we ok with the doc structure that we presently have? Do we have any action items here? If not, then...