Aryan Pingle

Another separate issue that arises because of the code duplication is that timestamps aren't left-padded with zeroes in Challenges: |Challenges|Tracks| |:-:|:-:| ||| I suppose we just need to add a...

Nice catch, yeah I second that proposal

Based on [this issue posted in `docker/build-push-action`](https://github.com/docker/build-push-action/issues/1093) and [this ongoing GitHub community thread](https://github.com/orgs/community/discussions/64967), it looks like the README file shown alongside a GitHub package **for a docker image** is that...

The best practice we could follow is to add links in the DTaaS repository README, something like: ``` Introduction |--- Intro to the repository |--- Intro to the Docker Image...

From my testing, the git and path options help in setting the "context" of the docker container, i.e. letting you access different repositories and their workflows. This doesn't seem to...

Here's the breakdown: ## Before PR #958 ```bash docker manifest inspect ${{ inputs.registry }}/${{ inputs.image-name }}:${{ inputs.version }} ``` We were assuming that the github repository owner would be `into-cps-association`...

Sure thing, I'll add it in a few

@prasadtalasila Looks like the logic works, except that: 1. The repository name should be in lowercase, which is easily fixed by [this solution](https://github.com/orgs/community/discussions/27086#discussioncomment-3254548). 2. The `publish-npm-package` job isn't checking if...

I can't find any API reference for GitHub's NPM Registry (`https://npm.pkg.github.com`). There is one for NPM: `https://registry.npmjs.org//`, but the same doesn't work for GH. The GH Packages page uses some...

Setting up the integrated GitLab instance contains several steps which require special attention. It is simply not feasible to perform these manually every time we need a clean installation. Thankfully,...