Saravanan666/pypi-org huggingface dataset:
Package: githubstars
Github StarsList repository stars and info through Github v4 GraphQL API$githubstars--langpython⭐38867awesome-python⭐31578httpie⭐30981thefuck⭐29831flask⭐29402youtube-dl$githubstarsdjango--langpython--count5--url--desc⭐28394django(https://github.com/django/django)-TheWebframeworkforperfectionistswithdeadlines.⭐13937sentry(https://github.com/getsentry/sentry)-Sentryisacross-platformcrashreportingandaggregationplatform.⭐8685django-rest-framework(https://github.com/encode/django-rest-framework)-WebAPIsforDjango.⭐5196django-cms(https://github.com/divio/django-cms)-Theeasy-to-useanddeveloper-friendlyCMS⭐4931Zappa(https://github.com/Miserlou/Zappa)-ServerlessPythonWebServicesInstallation$pipinstallgithubstars$exportGITHUB_API_TOKEN="<your token here>"Since Github require OAuth token to access GraphQL server, you must set personal access token first.Refer:Authenticating with GraphQLandCreating a personal access token for the command lineUsage$githubstars-husage:githubstars[-h][--lang][--count][--desc][--url][--verbose][--version][repo]ListrepositorystarsandinfothroughGithubv4GraphQLAPIpositionalarguments:reporepositorynametosearchoptionalarguments:-h,--helpshowthishelpmessageandexit--countnumberofrepositoriestoshow--descshowrepodescription--langsearchbasedonlanguage--new-createdcreatedthisweek--new-pushedpushedthisweek--urlshowrepourl--verboseshowrequestdetail--versionshowversionReferenceGitHub API | GitHub Developer GuideGraphQL API Explorer | GitHub Developer GuideCreating a personal access token for the command line - User DocumentationSearching repositories - User Documentation
Package: github-stats
Github StatsCommand line tool to get number of PRs reviewed by a user.UsageUse--helpto see all options.$ gitstats --help
Usage: gitstats [OPTIONS]

  This script will print the number of PRs reviewed by the user in the given
  timeframe.

Options:
  -t, --token TEXT            Github token
  -u, --username TEXT         Github username
  -o, --org TEXT              Github org
  -r, --repos TEXT            ',' separated github repos
  -s, --start_timestamp TEXT  Start time in epoch format
  -e, --end_timestamp TEXT    End time in epoch format
  --help                      Show this message and exit.The script by default attempts to read the options from the environment variables. Set the following environment variables:GITHUB_TOKEN- GitHub tokenGITHUB_USERNAME- GitHub usernameGITHUB_ORGANIZATION- GitHub organizationGITHUB_REPOS- Comma separated list of GitHub repositoriesIf the environment variables are not set, the script will prompt for the values.When the script is run, it will print the number of PRs reviewed by the user in the last two weeks.$ gitstats
Repos ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 2/2 • 0:00:06 0:00:00


╭───┬───────────┬─────────────────────────────────────────────────────────────────────┬───────╮
│   │ Repo      │ PR Title                                                            │ PR ID │
├───┼───────────┼─────────────────────────────────────────────────────────────────────┼───────┤
│ 0 │ gitrepo_1 │ Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiu │ 101   │
│ 1 │ gitrepo_2 │ Lorem ipsum dolor sit amet, consectetur adipiscing elit,            │ 100   │
╰───┴───────────┴─────────────────────────────────────────────────────────────────────┴───────╯

                       PRs reviewed between 2022-07-04 and 2022-07-18: 2
Package: github-status
A simple interface for updating SHA1s for PRs with statuses. Made for Jenkins
initially, altough a command line tool, it mostly consumes environment
variables to set states on commits.Github Environment Variables:GITHUB_REPOSITORYThe url part of the repo, like ceph/cephGITHUB_SHAA commit SHA that will receive the updateGITHUB_OAUTH_TOKENGenerated TOKEN to authenticate to GithubGITHUB_STATUS_CONTEXTThe “title” part of the status, like “docs”GITHUB_STATUS_STARTEDThe ‘started’ text that will change next to the ‘title’ (context)GITHUB_STATUS_SUCCESSThe ‘success’ text that will change next to the ‘title’ (context)GITHUB_STATUS_FAILUREThe ‘failure’ text that will change next to the ‘title’ (context)GITHUB_STATUS_ERRORThe ‘error’ text that will change next to the ‘title’ (context)GITHUB_STATUS_STATEThe state for the sha1, one of: ‘success’, ‘error’, ‘failure’, or ‘pending’Build Environment Variables:BUILD_URLA url that points to the actual full url for the buildPARENT_BUILD_URLOptional parent url where actual build happened
Package: github-status-checker
GitHub Status CheckerWhat this isA tool and Python module for checking the status of GitHub.InstallationInstall the module viapipmoose@rapid7:~$ pip install github-status-checker
...Usagemoose@rapid7:~$ github-status webhooks
Service 'Webhooks' is currently operational!ContributionsContributions are welcome! This project utilizesblackandpre-commitfor handling code
style. Simply follow the instructions for installing pre-commit and
runpre-commit installin the repository after cloning and you will
be on your way to contributing!Changelog1.0.2 - Update to handle crash on outage report | Code style: black
| Add contribution section1.0.1 - Update homepage and author name1.0.0 - Swap dataclasses for traditional classes for greater Python version
compatibility (Python 3.x+)0.1.0 - Initial development, support Summary
Package: github-status-cli
GitHub Status CLIA small command-line utility that returns current status and incident information from the GitHub API.Helpful to quickly check for service disruptions without switching apps when experiencing issues with git commands.Usage$github-status

----------------------------------------------------------------------------------------|GitHubStatus:AllSystemsOperational|----------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------|COMPONENT|STATUS|----------------------------------------------------------------------------------------|GitOperations|operational||APIRequests|operational||Webhooks|operational||Issues|operational||PullRequests|operational||Actions|operational||Packages|operational||Pages|operational||Codespaces|operational||Copilot|operational|----------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------|INCIDENT|IMPACT|STATUS|----------------------------------------------------------------------------------------|Therearecurrentlynoactiveincidents.|----------------------------------------------------------------------------------------InstallationUsingpip$pipinstallgithub-status-cliManually$gitclonehttps://github.com/mvanderlinde/github-status-cli.git
$cdgithub-status-cli
$python-mbuild
$pipinstalldist/github_status_cli-1.0.0-py3-none-any.whl
Package: github-summary
Aboutgithub-summaryis a python tool for generate github summary in multiple formats. It can generate a github summary in multiple formats (RST, TXT, HTML, etc …)InstallingTo install the latest release fromPyPI$ pip install github-summaryTo install the latest development version fromGitHub$ pip install git+git://github.com/badele/github-summary.gitUtilizationModify~/.github-summary.pyorconfig.py, for security reason, it is preferable modify~/.github-summary.pyand execute commandgithubsummary -t rst/index-en.rst -j example_projects.json -s example.rstOptionsYou can configure options by projects, options is stored in JSON format. Here an exemple of JSON options{
 "fabrecipes": {
     "hours": "89",
     "description": "A overwriting description text for fabrecipe."
 },
 "JobCatcher": {
     "hours": "108",
     "description": "Another overwriting description text for JobCatcher."
 },
 "gitcheck": {
     "hours": "15",
     "url": "http://bruno.adele.im/projets/gitcheck",
     "description": "Check multiple git repository in one pass."
 },
 "github-summary": {
     "coveralls": "True",
     "description": "Python tool for generate github summary in multiple formats (TXT, RST, HTML, ...)",
     "pypi": "True",
     "pydownload": "True",
     "hours": "30",
     "travis": "True"
 }
}You can also use the externals tools for populate the JSON file. Ex: Emacs Org file to JSON file (projects contributed time)org2json -o project.org -s example_projects.jsonYou can see the generatedexamplein RST formatYou can also see the result directely in my personnalwebsiteChangelogVersion 0.1.2 (2013-12-20)Add graph languages repartionsFix org2JSONAdd changelogAdd a projects indexChange JSON formatVersion 0.1.1 (2013-12-16)First version
Package: githubsurvivor
GitHub Survivor is a simple bug dashboard that shows an overview of bugs in an
external issue tracker. We use it at99designsto keep an eye on the bug
count and remind ourselves to close bugs.OverviewIt’s easy to forget about bugs when you’re knee-deep in feature development.
This dashboard is a good way to keep bugs on people’s minds, and to show
at-a-glance information about the current bug situation.GitHub Survivor scrapes your bug data using your issue tracker’s API and stores
it in a local Mongo DB for subsequent querying. It shows, at a glance:Top/bottom bug closers for the current reporting period (week, month or sprint)Current open bug countNet difference in open bugs since the last reporting periodCharts (yay!):Number of bugs opened/closed for the last 12 reporting periodsNumber of open bugs over the last 12 reporting periodsThere are bug trackers that provide this kind of data, but we wanted something
fun that integrates with our existing bug tracking solution.Supported issue trackersGitHub Survivor can integrate with these issue trackers out of the box:GitHubJIRA(courtesy ofjirasurvivor)Read more aboutdefining backendsin the wiki.Quick setupRequirements:Python >= 2.7MongoDBvirtualenv (recommended)This command might satisfy the above dependencies on Ubuntu:$ sudo apt-get install python2.7 mongodb python-virtualenvInstall package usingpip install githubsurvivorGenerate a configuration file usinggithubsurvivor-generate-configDo an initial import of your bugs usinggithubsurvivor-syncStart the server usinggithubsurvivorFor detailed instructions, seehttps://github.com/99designs/githubsurvivor/wiki/InstallationDevelopment notesSeehttps://github.com/99designs/githubsurvivor/wiki/DevelopmentLicenseMIT; seeLICENSEContributorsSeehttps://github.com/99designs/githubsurvivor/wiki/Contributors
Package: github-sync
This script uses the GitHub API to get a list of all your repos in your GitHub account. If the repo already exists locally, it will update it via git-pull.Unlikehttps://github.com/kennethreitz/ghsyncthis package does not require a directory structure, just point the way to the place where you have to find your repos. The default is “.” (current directory), set the correct path:export GITHUB_SYNC_DIR='/path/to/repos'InstallTo install github-sync, simply run:$ pip install github-sync
... or develop. version:
$ pip install -e git://github.com/adw0rd/github-sync.git#egg=github-syncThe commandgithub-syncwill then be available to you from the command line.$ github-syncHistoryThis fork has roots fromhttps://github.com/kennethreitz/ghsync/I wanted to get my fork is simpler, without the directory structure, etc.
And just to recursively searched github-repository at the specified path and performed git-pull
Package: github-tagged-release
GitHub tagged releaseGitHub changelogs using tags for your CircleCI workflow.Usagepipinstallgithub_tagged_release
github_tagged_releaseIn pythonfromgithub_releaseimportGitHubReleasegr=GitHubRelease()gr.create_release_from_tag()Example CircleCI workflow:version:2jobs:build:docker:-image:circleci/node:8steps:-checkout-npm install-npm testdeploy_prod:docker:-image:circleci/node:8steps:-run:name:Verify tag on master branchcommand:|git branch --contains | grep -q '^[ |*] master$'-run:name:Deploycommand:npm run deploy-run:name:Create GitHub releasecommand:|pip install --user github-tagged-releasepython ~/.local/bin/github_tagged_releaseworkflows:version:2build_test_hold_deploy:jobs:-build:filters:tags:only:/.*/-deploy_prod:requires:-buildfilters:tags:only:/^v[0-9]+(\.[0-9]+)*$/branches:ignore:/.*/
Package: github-team-organizer
github-team-organizerPython way to organize permissions in your organizationSettingsSome options can be set via an environment variable (real ordotenv) or command line flag.Environment variable nameCommand line flagDescriptionGITHUB_API_KEY-k/--api-keyGitHub API keyGITHUB_ORGANIZATION-o/--orgGitHub Organization which we will operate onUsageYou have two options to execute this script:Apply mode(-aor--apply) - real changes will be done through executionTest mode(-tor--test, default) - API will be scanned and proposed changes will be reported as output, no real changes will be performed
Package: github-timeline-rss
Github timeline to RSS translation for easier feed integrationFree software: MIT licenseFeaturesCreate RSS feeds from github timelinesCommand line interface to dump to stdout or a fileUsageOptional: set up virtualenv environment with:virtualenv venv
source venv/bin/activateInstall requirements:pip install -r requirements_dev.txtRun flask app, e.g.:cd github_timeline_rss
FLASK_APP=rss.py flask runTest:http://127.0.0.1:5000/narfman0Should show rss feed for activity for narfman0 from github!CLIThe command line interface may be used to dump a timeline to stdout:github_timeline_rss narfman0or it may be directed at a file with–file:github_timeline_rss narfman0 --file narfman0.atom
Package: github-to-colab-link
Github to Colab Link GeneratorSometimes you may want to load a Jupyter notebook from your repo to colab and run it there. Other times you may just want to add a colab link to your repositories readme page. Sure you can download a notebook and then import to colab but that may not always be ideal. The goal of this cli tool is to short-circuit that process so that you don't have to go through the extra clicks.Pre-requisitesThe repo where your notebook is must be publicInstallation and UsageInstall from pippipinstall-Ugithub-to-colab-linkUsageThe package currently generates links in two formats, one is a plain string, which you can copy and load in an web browser; another is a markdown embed which you can use in your markdown style docs, e.g. Github readmes.# for plain stringcolab-link-gen--string--ghlink_to_notebook# examplecolab-link-gen--string--ghhttps://github.com/ShawonAshraf/jax_examples/blob/main/playground/palmers_penguins.ipynb# for markdown embedcolab-link-gen--md--ghlink_to_notebook# examplecolab-link-gen--md--ghhttps://github.com/ShawonAshraf/jax_examples/blob/main/playground/palmers_penguins.ipynbDevClone the repoCreate avirtualenvInstall the requirementspipinstall-rrequirements.txtThe entrypoint for the cli tool is incli.py(therun()function)link.pycontains the helpers to generate the linksTestingpython-munittestdiscover-s./tests-p"*_test.py"
Package: github_token
GitHub TokenCreating an app token might not be the simplest task, use this utility
and forget about all the issues.Installpip install github_tokenUsageimport github_token
user = input("Username: ")
password = getpass.getpass()
app_name = input("App Name to create: ")
token_factory = github_token.TokenFactory(user, password, app_name,
                                          github_token.Scopes.all)

print(token_factory(
    tfa_token_callback=lambda: input("TFA Token: ")
))
Package: github-token-app
Github Token AppGithub Token App is a package for generating short lived github tokens (expires in 1 hour) with minimum necessary permissions.Currently, the code generates read and write github token to the specific list of repositories.An example of read github token is git clone.An example of write github token is git push.The github token app also provides a CLI which can be used to generate a github token to authenticate to github.Installationpipinstallgithub-token-appRequired Environment VariablesBASE64_PRIVATE_PEM_KEY: This is the private pem key for the github-app encoded in base64.GITHUB_APP_ID: App IDINSTALLATION_ID: Installation Id for App/Org Pair (if you don't know, it can be generated from the second step below)What the code does?The code is for authenticating agithub app as an installation. Installations are created from a Github app settings (Install App).Under Install App, click on the account settings. You will find the installation ID in the URLhttps://github.com/apps/my-app-name/installations/**INSTALLATION_ID**. Set theINSTALLATION_IDas environment variable based on your required access.Alternatively, the code containsget_installationsfunction which can be called by CLI commandgta installations. It returns a response of list of installations. Theidattributes in the responses are the installation ids.Finally, there are three methods read, write and write-pr. That generates token to perform respective actions to specific repositories.CommandsreadGenerates token which grants read-only access to specified Github Repositorygtaread[listofrepositories]gtareadmy-private-repowriteGenerates token which grants write access to specified Github Repositorygtawrite[listofrepositories]gtawritemy-private-repowrite-prGenerate token which grants write access to specified Github Repository along with permission to create prs.gtawrite-pr[listofrepositories]gtawrite-prmy-private-repoUsing the generated tokenCloning a repositorygitclonehttps://x-access-token:$GITHUB_TOKEN@github.com/my-org/my-private-repo.gitWriting to a repositorygitremoteset-urlorigin"https://x-access-token:${GITHUB_TOKEN}@github.com/my-org/my-private-repo.git"gitconfig--globaluser.email"<>"gitconfig--globaluser.name"my-username"ContributionPlease read the CLA carefully before submitting your contribution to Mercari.
Under any circumstances, by submitting your contribution, you are deemed to accept and agree to be bound by the terms and conditions of the CLA.https://www.mercari.com/cla/LicenseCopyright 2021 Mercari, Inc.Licensed under the MIT License.
Package: githubtools
Some commandline tools for interacting with github.=====================Things you can do:- Set commit status- Create a pull request- Merge a pull request- MergeSet Status on a commit:Usage:github-commit-status -c <commit-hash> -s <status> -u <github-username> -p <github-password> -r <github_repo> --url <URL> --context <context> -d "<description>"github-commit-status -c <commit-hash> -s <status> -t <github-token> -r <github_repo> --url <URL> --context <context> -d "<description>"Options:-c <commit-hash>, --commit-hash <commit-hash>  Github commit hash-s <status>, --status <status>  Status to set [pending, success, error, or failure]-u <username>, --username <username>  github username-p <password>, --password <password>  github password-t <token>, --token <token>  github access token-r <repository>, --repo <repository> github repository-d <description> --description <description> description of the status--url <url> URL to refer back to--context <context> The context of the status.  Typically the name of the service creating the status.Create a pull request:Usage:github-create-pull-request -h <head> -b <base> -t <token> -r <repo> [-d "<description>" --title <title>]Options:-h <head>, --head <head>  Head: the branch you're pulling from.-b <base>, --base <base>  Base: the branch you're pulling to.-t <token>, --token <token>  github access token-r <repository>, --repo <repository> github repository-d <description> --description <description> The pull request description.--title <title>  The pull request title.Merge a pull request:Usage:github-merge-pull-request (-h <head> -b <base> | -p <pull-number>) -t <token> -r <repo>Options:-h <head>, --head <head>  Head: the branch you're pulling from.-b <base>, --base <base>  Base: the branch you're pulling to.-t <token>, --token <token>  github access token-r <repository>, --repo <repository> github repository-p <pull-number> --pull-number <pull-number> The pull request ID number.MergeUsage:github-merge -h <head> -b <base> -t <token> -r <repo>Options:-h <head>, --head <head>  Head: the branch you're pulling from.-b <base>, --base <base>  Base: the branch you're pulling to.-t <token>, --token <token>  github access token-r <repository>, --repo <repository> github repositorySee https://github.com/nricklin/githubtools
Package: github-traffic
github-trafficSummarize Github traffic stats across reposInstallLatest stable:$ pip install --user github-trafficLatest pre-release:$ pip install --user --pre github-trafficGit:$ pip install --user git+https://github.com/jashandeep-sohi/github-traffic.gitUsageViews & clones summary:$ github-traffic --token "$GITHUB_TOKEN" summaryViews summary:$ github-traffic --token "$GITHUB_TOKEN" summary --metrics viewsClones summary:$ github-traffic --token "$GITHUB_TOKEN" summary --metrics clonesTop referrers:$ github-traffic --token "$GITHUB_TOKEN" referrersTop paths:$ github-traffic --token "$GITHUB_TOKEN" paths
Package: github-traffic-stats
Get statistics on web traffic to your GitHub repositories.Python CLIPython CLI tool to get web traffic stats on the command line using the
GitHub API.A few use cases to show why this may be useful.Checking the volume of traffic to all of your repos. Monitor sudden
spikes in interest or any general patterns.Storing the traffic stats for future reference.Checking how often your code is cloned.Installationpip install github_traffic_statsDependenciesRequests (kennethreitz/requests)Install the requirements by running:pip install -r requirements.txtThere are a number of GitHublibrariesfor Python and other
languages, although they may not support the Repository Traffic API
(announced on August 15, 2016).Usageusage: gts [-h] username [repo] [save_csv] [-o]
   or:
usage: gts [-h] username:password [repo] [save_csv] [-o]

positional arguments:
  username    Github username
  password    Github password for 'username', or access token
  repo        User's repo
  save_csv    Set to "no_csv" if no CSV should be saved

optional arguments:
  -h, --help  show this help message and exit
  -o, --organization specify Github organization if different from usernameInformation onGithub Access Tokens.RunRun on the command line with eitherpythonorpython3.$ gts 'nchah' 'github-traffic-stats' 'save_csv'
Password:* (passwords are hidden)
> github-traffic-stats - Visitors
Date        Views   Unique visitors
Totals      125     36
2017-07-16  1       1
2017-07-17  10      2
2017-07-19  11      4
2017-07-20  12      5
2017-07-21  3       3
2017-07-22  1       1
2017-07-23  1       1
2017-07-24  17      6
2017-07-25  32      5
2017-07-26  1       1
2017-07-27  1       1
2017-07-28  6       4
2017-07-29  26      5
2017-07-30  3       1

> github-traffic-stats - Git clones
Date        Clones  Unique cloners
Totals      5       5
2017-07-17  1       1
2017-07-24  2       2
2017-07-26  1       1
2017-07-29  1       1

> github-traffic-stats - Referring sites
Date        Views   Unique visitors
Totals      44      27
Google      33      24
github.c... 11      3


$ # Or to get stats on all of your repositories
$ gts 'nchah' 'ALL' 'save_csv'
Password:* (passwords are hidden)

$ # Or if you are running on an organization repo (for example NREL's SAM repo) as a user with access
$ gts 'nickdiorio' 'SAM' 'save_csv' -o 'NREL'
Password:* (passwords are hidden)
...Traffic data stored in CSV files with columns:repository_name, date, views, unique_visitorsSeparate CSVs are created for each run of the script.To merge and only preserve the unique data points, run:$ bash bash/merge-csv.sh [folder_with_CSVs]DocumentationA list of the references used for this project.GitHub APIPreview the Repository Traffic API (August 15, 2016)