> https://objects.githubusercontent.com/github-production-release-asset-2e65be/61855572/d9f0b98c-6f37-11e7-99c0-e16770847719?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=releaseassetproduction%2F20241211%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20241211T051051Z&X-Amz-Expires=300&X-Amz-Signature=9369e9dea3a38c8f201fc758e9f89a88c7abf22bba7d0b2553a4a3b309a1d89d&X-Amz-SignedHeaders=host&response-content-disposition=attachment%3B%20filename%3Dterminal-0.0.10.vsix&response-content-type=application%2Foctet-

Open
#50 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
1/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale

Research direction

The issue contains only a quoted GitHub release-asset URL and a reference to FileExplorer issue 55; it names no files, tests, or entry points. Review the referenced issue and confirm the intended problem before identifying a repository change and a verifiable definition of done.

Written by the indexing model from the issue text.

Description

          > https://objects.githubusercontent.com/github-production-release-asset-2e65be/61855572/d9f0b98c-6f37-11e7-99c0-e16770847719?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=releaseassetproduction%2F20241211%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20241211T051051Z&X-Amz-Expires=300&X-Amz-Signature=9369e9dea3a38c8f201fc758e9f89a88c7abf22bba7d0b2553a4a3b309a1d89d&X-Amz-SignedHeaders=host&response-content-disposition=attachment%3B%20filename%3Dterminal-0.0.10.vsix&response-content-type=application%2Foctet-stream

Originally posted by @Aaxvcdchx in https://github.com/MiCode/FileExplorer/issues/55#issuecomment-2533664416

Dominant language
No language data
Stars
136
Forks
65
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from MiCode/kernel_devicetree

All issues in MiCode/kernel_devicetree

Similar issues

More Operating Systems issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.