Skip to content

config: add Visual Studio Code config compatible with fpb-lint #6829

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

davorpa
Copy link
Member

@davorpa davorpa commented Apr 15, 2022

What does this PR do?

Improve repo

For resources

Description

In the past, somebody had used VisualStudioCode to edit files with the bad lucky that this project doesn't have config compatible with fpb-lint. Thus, extra modifications are made when edit or commit files.

Moreover, people use to have installed markdownlint or markdown all-in-one addons to speed up somethings like TOC index or other stuff

Why is this valuable (or not)?

This PR adds the config necessary to minimize this kind of issues again. The config is parametrized (there where could be applied) according to remark config selected to free-programming-books-lint project

Checklist:

Follow-up

  • Check the status of GitHub Actions and resolve any reported warnings!

@davorpa davorpa self-assigned this Apr 15, 2022
@davorpa davorpa added the New Feature New feature / enhancement / translation... label Apr 15, 2022
@davorpa davorpa marked this pull request as ready for review April 15, 2022 19:35
@LuigiImVector LuigiImVector added help wanted Needs help solving a blocked / stucked item 👀 Needs Review Is this really a good resource? Reviews requested. labels Apr 16, 2022
@eshellman
Copy link
Collaborator

yes, need someone with expertise to review

1 similar comment
@eshellman
Copy link
Collaborator

yes, need someone with expertise to review

GH05T-HUNTER5

This comment was marked as resolved.

@Thenlie
Copy link
Contributor

Thenlie commented Nov 3, 2023

I haven't noticed any issues using VS Code. Maybe this is no longer relevant?

Copy link

'This Pull Request has been automatically marked as stale because it has not had recent activity during last 60 days 😴

It will be closed in 30 days if no further activity occurs. To unstale this PR, draft it, remove stale label, comment with a detailed explanation or push more commits.

There can be many reasons why some specific PR has no activity. The most probable cause is lack of time, not lack of interest.

Thank you for your patience ❤️'

@github-actions github-actions bot added the stale Requests that have not had recent interaction (Out-of-Date) label Apr 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
👀 Needs Review Is this really a good resource? Reviews requested. help wanted Needs help solving a blocked / stucked item New Feature New feature / enhancement / translation... stale Requests that have not had recent interaction (Out-of-Date)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants