-
Updated
Apr 3, 2020
pull-requests
Here are 419 public repositories matching this topic...
No documentation for working in the development environment and mocking things like users with X PRs.
Expected Behaviour
We should prepare Derek for use as an SDK/package so that he can be run on any platform - a Go microservice, AWS Lambda, Heroku etc.
This is the first ste
-
Updated
May 22, 2020 - JavaScript
-
Updated
Feb 3, 2018 - JavaScript
we create a lot of issues that are reserved for first-time contributors, like this one: hoodiehq/camp#37
It would be great to see on first sight if they sent PRs in the past. But so far the badge gets only added to comment of the author of the issue. Could we change that?
-
Updated
Mar 6, 2020
Improve the UI [Hacktoberfest 2019]
Would you like to work on this Project?
yes
UI design link will be submitted soon!!
-
Updated
Feb 24, 2020 - JavaScript
-
Updated
May 9, 2020 - Go
Love the product so far. Was wondering if there was an action to update the base branch that a pull request is compared to? If not, I think that would be a great feature to add. Something along the lines of:
pull_request_rules:
- name: Change base
conditions:
- "title~=^\\[Release\\].+"
actions:
change_base:
branch: release
-
Updated
Nov 25, 2019 - Scala
-
Updated
Feb 6, 2017 - Python
-
Updated
May 19, 2020 - JavaScript
-
Updated
Feb 22, 2020 - JavaScript
-
Updated
May 21, 2020 - C++
Is your feature request related to a problem? Please describe.
Currently, some coding style of Liquid and YAML are not unified. This is a bit confusing when writing codes for pull requests.
Example 1: Should we add spaces or not?
<
Add your blog
Add any blog of yours (preferably technical) to the Blogs
directory. Make sure to use most of the markdown features. Here's the link to markdown guide:
https://guides.github.com/features/mastering-markdown/
We want to display the number of items from a filtered list
Why
So we have an idea of how many items we have in that collection of filters.
Level
Beginner
usefull links
Screenshot attached
<img width="316" alt="Screenshot_2019-11-08_at_19 13 06" src="https://user-images.githubusercontent.com/88840/77308353-1f
It would be great to have a list of commands in a help page when using git pull-request --help
to know the full extent of the functionality of this package, thanks.
-
Updated
Mar 16, 2020 - Shell
If a user has a repo configured with remote
$ git config --local --get remote.origin.url
gh:myuser/myrepo
and a configuration ~/.ssh/config
(docs)
Host gh
HostName github.com
User git
then this configuration will map gh:myuser/myrepo
to the appropriate git@github.com:myuser/myrepo
when used with `git
-
Updated
Mar 7, 2019 - C++
Hi, I think that either the blacklist/whitelist has a bug, or the documentation is incorrect/misleading.
The documentation states 'The blacklist takes precedence over whitelist. I.e. a branch will not be built if the blacklist pattern matches to the branch name'.
On our setup we have 'master' as the blacklist pattern, and * as the whitelist pattern, which I assume to mean build any branch
More work
Thanks @sindresorhus for the advice!
The list needs a lot of work. It's not very useful as is. What would make it useful is if each entry had good commentary on why the pull request is awesome and what the submitter did right (bonus: what the submitter could have done better).
Better documentation
This project looks very interesting to me. However, could you add a little more detail documentation on how to, for example, starting with just a dockerfile/helm chart, create an environment. (I mean, I could not even see a 'how to install' section)
Improve this page
Add a description, image, and links to the pull-requests topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the pull-requests topic, visit your repo's landing page and select "manage topics."
From @chrisdias: