Add Two new Features (from Helpers4)

[Bérenger (baxyz)]

What type of PR is this?

• Add a new dev container collection
• Update to an existing dev container collection
• Documentation/spec update
• Other containers.dev site update (UX, layout, etc)

Related Issues

• Related Issue #
• Closes #

Description

• Migrates archived baxyz' Features (Git Absorb, Shell History Per Project) to the helpers4' Features while keeping the maintainer.
• Adds two adjacent helpers4 Features: Angular Dev and Local Mounts.
• Removes the obsolete Biome entry.
• Aligns names by dropping the “Feature” suffix.

Collection checklist

If your PR contributes a new collection, please utilize this checklist:

• Collection name: Git Absorb / Shell History Per Project / Angular Dev / Local Mounts
• Maintainer name: baxyz
• Maintainer contact link: https://github.com/helpers4/devcontainer/issues
• Repository URL: https://github.com/helpers4/devcontainer
• OCI Reference: ghcr.io/helpers4/devcontainer/
• I acknowledge that this collection provides new functionality, distinct from the existing collections part of this index.

[Bérenger (baxyz)]

@microsoft-github-policy-service agree

[Abdurrahmaan Iqbal (abdurriq)]

Hello Bérenger (@baxyz), thank you for your contribution. Since these features are all part of the same repo, could you combine these all into a single entry. I know it's a bit tricky for the title, but it reduces the cardinality of the features list.

@Kaniska244 Could we please look out for this going forward to avoid features being listed from the same repo as individual items.

[Bérenger (baxyz)]

Hi Abdurrahmaan Iqbal (@abdurriq), thank you for the feedback. I understand the concern about reducing cardinality in the features list.

However, I'm concerned that combining these features into a single entry would negatively impact discoverability and usability.

Could you clarify the preferred approach? Would it be acceptable to:

• Use a long name that combine features' name?
• Or is there a specific naming/grouping pattern you'd recommend that maintains searchability?
• Or do I use directly the repo name?

I'm happy to make the necessary changes once I understand the preferred direction.

[Abdurrahmaan Iqbal (abdurriq)]

Hmm, looking at the list we have accepted individual features listed as separate entries since the begining. I'll merge this for now, and we can think about what to do going forward.

[Abdurrahmaan Iqbal (abdurriq)]

Looking back at a comment from the previous maintainer, I see that I misunderstood what he meant.

Sorry, missed this before approving. Can you make these all a single collection? The oci reference should be http://ghcr.io/caspersg/devcontainer_features. We have a script that will automatically get all your features onto the website as long as they belong to that repo. Thanks!

It seems that we require a single entry per repo, and the individual features will be automatically detected and added as individual entries by our crawler. If you could make this change as a new PR, I would appreciate that.