Skip to content

Commit

Permalink
Test (#17)
Browse files Browse the repository at this point in the history
* Test Push

* Update 17-Youtube_api.Rmd

Test ob richtige Vorgehensweise
  • Loading branch information
dlajic authored Feb 4, 2022
1 parent e9099cd commit 481b222
Showing 1 changed file with 2 additions and 0 deletions.
2 changes: 2 additions & 0 deletions 17-Youtube_api.Rmd
Original file line number Diff line number Diff line change
Expand Up @@ -9,6 +9,8 @@ knitr::opts_chunk$set(warning = FALSE, message = FALSE, cache=TRUE)

## Provided services/data

#test for pull request

* *What data/service is provided by the API?*

The API is provided by Google, Youtube’s parent company.
Expand Down

5 comments on commit 481b222

@chainsawriot
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Warum wurde das im Main gemergt?

@paulcbauer
Copy link
Owner

@paulcbauer paulcbauer commented on 481b222 Feb 4, 2022 via email

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@clandesv
Copy link
Collaborator

@clandesv clandesv commented on 481b222 Feb 4, 2022 via email

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@chainsawriot
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@clandesv @paulcbauer One way to deal with that is to create a branch in this repo (let's say "youtube"). When Dean made a PR, you can select which base branch to merge to. You can merge it first to the "youtube" branch. When you satisfy with the changes in the "youtube" branch, merge (probably "squash and merge") the "youtube" branch to "main" branch.

@clandesv
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@chainsawriot many thanks!

Please sign in to comment.