Creating and maintaining documentation is increadibly important. When needed, as part of this PR you need to tackle this too.
- Documentation was created. URL to docs:
- Documentation was updated. URL to docs:
- Changes did not need documentation updates.
| #!/usr/bin/env sh | |
| echo "1234" | gpg --no-use-agent -o /dev/null --local-user <KEYID> -as - && echo "The correct passphrase was entered for this key" |
| [user] | |
| name = Froilán Irizarry Rivera | |
| email = | |
| signingkey = | |
| [core] | |
| excludesfile = ~/.gitignore_global | |
| editor = nano | |
| quotepath = false |
| alias findbin='find . -type f -not -path "./.git/*" -exec perl -MFile::Basename -e '\''print (-T $_ ? "" : (fileparse ($_, qr/\.[^.]*/))[2] . "\n" ) for @ARGV'\'' {} + | sort | uniq' |
| const { Octokit } = require('@octokit/rest'); | |
| const { throttling } = require('@octokit/plugin-throttling'); | |
| const OctokitThrottling = Octokit.plugin(throttling); | |
| const octokit = new OctokitThrottling({ | |
| auth: "your-token", | |
| throttle: { | |
| onRateLimit: (retryAfter, options) => { | |
| octokit.log.warn( |
This is a quick and simple example on how we can use a template engine to create markdown strings for use in GitHub issues or Jira ticket.
Eta.js is a templating engine that embbeds Javascript syntax into the template it self. It seems super lite weight.
When working with issues and PRs, a ton of the code we do are the message templates themselves. I think that extracting this into a template engine will clean up the business logic from the view logic (sound familiar 😉).
This guide on how to convert an SVN repository to a git repository was mostly taken from John Albin Wilkins post on Converting a Subversion repository to Git.
Prompt one
Company: Acme computers
Version control platform(s): Many GitHub Enterprise instances installed throughout the company by different teams. Acme Computers is trying to standardize on GitHub Enterprise and consolidate their GitHub usage onto a single instance. The company has many instances of other Git hosting solutions installed as well. Some are fully supported applications. Other instances are on machines under people's desks.
Customer requests: