https://github.com/nikhils4/youtube-ad-skipper

Extension is live, find the link in README
https://github.com/nikhils4/youtube-ad-skipper

Last synced: about 2 months ago
JSON representation

Extension is live, find the link in README

• Host: GitHub
• URL: https://github.com/nikhils4/youtube-ad-skipper
• Owner: nikhils4
• License: bsd-3-clause
• Created: 2018-12-16T21:29:10.000Z (about 6 years ago)
• Default Branch: master
• Last Pushed: 2024-07-13T07:07:36.000Z (6 months ago)
• Last Synced: 2024-07-13T08:25:11.934Z (6 months ago)
• Language: JavaScript
• Homepage:
• Size: 40 KB
• Stars: 2
• Watchers: 1
• Forks: 3
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# Welcome to Youtube-ad-skipper

Youtube-ad-skipper ia a project aimed at skipping the skippable youtube ads. Check [Ad Abolish](https://chrome.google.com/webstore/detail/youtube-ad-skipper/jfmmhlgdaekimamaebokgdjeolkdlfpg?hl=en)

# Contributing

Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change.

## Opening or finding an issue

OPENING AN ISSUE:

You should usually open an issue in the following situations:

Report an error you can’t solve yourself

Discuss a high-level topic or idea (for example, community, vision or policies)

Propose a new feature or other project idea

FINDING AN ISSUE:

If you found an open issue that you want to tackle, comment on the issue to let people know you’re on it. That way, people are less likely to duplicate your work.

If an issue was opened a while ago, it’s possible that it’s being addressed somewhere else, or has already been resolved, so comment to ask for confirmation before starting work.

## Opening a pull request

You should usually open a pull request in the following situations:

Submit trivial fixes (for example, a typo, a broken link or an obvious error)

Start work on a contribution that was already asked for, or that you’ve already discussed, in an issue

### Forking a repository

Fork the repository and clone it locally. Connect your local to the original “upstream” repository by adding it as a remote. Pull in changes from “upstream” often so that you stay up to date so that when you submit your pull request, merge conflicts will be less likely.

Create a branch for your edits.

Reference any relevant issues or supporting documentation in your PR (for example, “Closes #37.”)

Include screenshots of the before and after if your changes include differences in HTML/CSS. Drag and drop the images into the body of your pull request.

Test your changes! Run your changes against any existing tests if they exist and create new ones when needed. Whether tests exist or not, make sure your changes don’t break the existing project.

###  Steps to make a Pull Request

```bash

git clone https://github.com/your_github_username/Youtube-ad-skipper.git

cd  Youtube-ad-skipper

git checkout -b branchname

git diff

git add -A

git status

git commit -m "Write the change you have made"

git status

git push origin branchname

```

## And Voila, you have made your first PR!