* Drop Travis CI
* Update DEPLOY.md about new workflow of uploading new version to PyPI
* Upload coverage data to Codecov
Co-Authored-By: Steve Kowalik <steven@wedontsleep.org>
* Fix bug in repository create new file example (#1211)
the previous code would throw an 'error path cannot start with a slash'
. Now fixed it by removing a slash in the example.
Fixes: #1210
Clean up a few errors I missed, ignore another, and configure flake8 using
a config file to ignore certain errors. The next step would be to remove
the F* ignores.
The previous code would prematurely exit when the intermediate contents list holds one thing, and that one thing has not been processed / expanded yet. Now the exit condition is when the contents list is empty, and there is nothing left to be processed.
Added support for the traffic endpoints found at https://developer.github.com/v3/repos/traffic/.
We added four functions to the Repository class (one for each of the endpoints) with corresponding unit tests.
Fixes#926
Wraps the parts of the notification API that allows the user to mark notifications as read.
New methods are :
- Notification.mark_as_read : marks a single notification thread as read
- Repository.mark_notifications_as_read : marks all the notifications for a given repository as read
- AuthenticatedUser.mark_notifications_as_read : marks all the notifications as read
Aims to fix : https://github.com/PyGithub/PyGithub/issues/571 and simply uses the APIs described on this page : https://developer.github.com/enterprise/11.10.340/v3/activity/notifications/
A weird thing I noticed doing this is that Repository.notifications_url doesn't seem to be usable directly. I used Repository.url + "/notifications" instead.
* Add a trailing slash to URL when updating or deleting a file.
* Update test files to match new create/update/delete_file Repo methods
* Add trailing slash to get_contents() method
* update tests
* add missing slash in get_dir_contents
* add example usage
* remove dup slashes in tests
* clarify example comments
## What does this change do?
Adds a small example of how to get at the date a commit took place.
### Changes
#### doc/examples/Commit.rst
Adds a block of code that demonstrates how to get at a commit's date.
## Motivation
This example is in the spirit of #874.
When I began using PyGithub it was not readily apparent to me where the commit date was being abstracted to. Being unfamiliar with Git's API, it took some convincing for me to be satisfied that the `Commit.commit.author/committer.date` path would get me the commit date.
I would hope that this would save somebody a little bit of time in the future.
## How has this been tested?
I've built the docs locally and made sure the HTML is generated as expected.
## Screenshots
This PR add the follow code examples
* Issue examples (get list, get specific issue, create issue)
* Milestone examples (get list, get specific milestone, create milestone)
Ref.: https://github.com/PyGithub/PyGithub/issues/874
Steve Kowalik
