Hello, I found your cool project from the 1.40.0 release notes. I noticed the recent uptick in issues and was wondering if this correlated to a recent release. Would it be feasible and desirable to add tagged releases/tags to the chart?

The hourly chart includes grid lines to separate each day out. I want to add this to the 10-day chart as well.

It would be nice to see a timeline from day 1 of the project till the current day.
Specially since September was such an interesting month.

As it has been mentioned to me, there has been a good 500 issues that have been opened since I started this so, when I said there has been about 1000 issues closed, technically there actually is about 1500, so switch the number at the bottom to be represented by the number of new closed issues since Sept 10

It would be nice to scrub left and right on a mobile device and be able to see a larger amount of history

buisinesses instead of businesses.

A few people have commented that the data can get a little misleading if the y-axis labels are not in the viewport of the screen. Even though it does have labels with relative min and max values, looking directly at the data itself can be misleading to some so enforcing the y-axis to start at 0 may fix that.

Add a small bit of CSS to make the page fit without having text touching the edges of a phone

Every so often, the Lambda function which goes and checks for the hourly issue count does not properly authenticate for some reason and does not end up saving an entry in the database.

Many people have requested how this was made and as well, I myself want to make other websites that have a very similar infrastructure for GitHub-based statistic trackers.

Currently everything was manually setup while I believe a better situation is to have a more structured and laid out base. Tasks such as provisioning the various functions and databases to be a one command deploy after minimal config setup would be the ideal situation. A product that a developer can create graph visualizations and find insights into codebases.

I am wanting to dive into centralizing towards a solution that could be used either with cloud software or entirely on-prem. Here are some ideas for such I currently have (and if you can think of ways of doing these things that may be better or different than what I think, please add a comment below with such).

On-prem:

• Switch from firebase to some self-hosted database (Either NoSQL or Relational Databases could work for this)
• cronjobs / systemd timers to set up scheduled scripts?

Cloud-based:

• centralize to as few cloud providers as possible / work to allow transfer between clouds be as painless as possible
• setup orchestration workflow to spin up resources (AWS CloudFormation, Azure Resource Manager, Terraform, etc)
• Add monitoring for the infrastructure

as title says

whenever I try to make a new text file this happens so the extension wont work.
Downloading package '.NET Core Debugger (Windows / x64)' Failed to download from https://vsdebugger.azureedge.net/coreclr-debug-1-25-1/coreclr-debug-win7-x64.zip. No content-length header
Failed at stage: downloadPackage
Missing content-length

Document the setup process for the vscode-issue-tracker.

The architecture is currently across multiple clouds (AWS, GCP, Azure (likely)), which has a bit of complexity, so making sure that everything is detailed.

• AWS Lambda for the function to hit the GitHub API and store data to Firebase Firestore database
• Firebase Firestore (GCP) to store data from GitHub API
• Frontend currently hosted on netlify (but can technically be on any hosting provider)

It would be nice to see a timeline of open issues for the last year. This is similar to #13, but that issue asks for all history. So all in all, I think it would be valuable to see:

• Last 3 Days
• Last Month
• Last Year
• All time