Skip to content

Conversation

@Aviraj2929
Copy link

What does this PR do?

Add resource(s) | Remove resource(s) | Add info | Improve repo

IMPORTANT

  • Read our contributing guidelines.
  • Is this a revision of a previously submitted PR? If so, STOP! Go back, reopen the PR, and add commit(s) the branch you previously submitted. Please don't make the job of reviewing more difficult by hiding previous work.

For resources

Description

Why is this valuable (or not)?

How do we know it's really free?

For book lists, is it a book? For course lists, is it a course? etc.

Checklist:

  • Search for duplicates.
  • Include author(s) and platform where appropriate.
  • Put lists in alphabetical order, correct spacing.
  • Add needed indications (PDF, access notes, under construction).
  • Used an informative name for this pull request.

Follow-up

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

@github-actions
Copy link

Linter failed, fix the error(s):

free-programming-books/courses/free-courses-aj.md
261:1-279:100  warning  Incorrect number of blank lines between last section and next heading  blank-lines-1-0-2  remark-lint

free-programming-books/courses/free-courses-al.md
261:1-279:100  warning  Incorrect number of blank lines between last section and next heading  blank-lines-1-0-2  remark-lint
307:1-312:111  warning  Incorrect number of blank lines between last section and next heading  blank-lines-1-0-2  remark-lint

@github-actions github-actions bot added the linter error Please, correct build errors found by linter! label Oct 23, 2025
@github-actions
Copy link

Linter failed, fix the error(s):

free-programming-books/courses/free-courses-aj.md
261:1-279:100  warning  Incorrect number of blank lines between last section and next heading  blank-lines-1-0-2  remark-lint

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

linter error Please, correct build errors found by linter!

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant