get_issue_events | R Documentation |
In addition to information returned by GitHub API, appends field "number" for the issue number to which the returned events correspond.
get_issue_events(ref, number, dummy_events = TRUE)
ref |
Repository reference (list) created by |
number |
Number of issue |
dummy_events |
Logical for whether or not to create a 'dummy' event to denote the existence of issues which have no events. Defaults to TRUE (to allow creation). Default behavior makes the process of mapping over multiple issues simpler. |
Content of GET request as list
Other issues:
get_issue_comments()
,
get_issues()
,
parse_issue_comments()
,
parse_issue_events()
,
parse_issues()
,
post_issue_update()
,
post_issue()
,
report_discussion()
,
report_progress()
,
viz_waterfall()
Other events:
parse_issue_events()
## Not run:
myrepo <- create_repo_ref('emilyriederer', 'myrepo')
# single issue workflow
events_res <- get_issue_events(myrepo, number = 1)
events <- parse_issue_events(events_res)
# multi-issue workflow
issue_res <- get_issues(my_repo, state = 'open')
issues <- parse_issues(issues_res)
events <- purrr::map_df(issues$number, ~get_issue_events(myrepo, .x) %>% parse_issue_events())
## End(Not run)
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.