Readme contains outdated information ?

Open
#2,328 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
csharp, github-actions
Domain
ci-cd, documentation

Research direction

Start in the repository README and inspect the Gitter link and the invalid build badge URL. Check the GitHub Actions configuration to determine whether a current build status can be linked; done means removing the obsolete link and correcting or removing the invalid build reference.

Written by the indexing model from the issue text.

Description

The readme is pointing to gitter where the last question was in 2019 and the build link is pointing to https://camo.githubusercontent.com/78260d2f0cf651f1bf48faa0908915beb8f39551c235642c75a851b36f3de97b/68747470733a2f2f6465766469762e76697375616c73747564696f2e636f6d2f5f617069732f7075626c69632f6275696c642f646566696e6974696f6e732f30626462633539302d613036322d346333662d623066362d3933383366363738363565652f343439322f6261646765 which is invalid for me.

I can provide a PR to remove the gitter link as I think it is not engaging for anyone looking at this but I do not know where are the build? GitHub Actions seems quite empty.

Dominant language
C#
Stars
1.8k
Forks
355
No merged PRs in 30d

Contributor guide

Open the contributing guide

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 microsoft/nodejstools

All issues in microsoft/nodejstools

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.