- Activity on a given project can be observed by looking at when the last commit was made.
- In case issues and pull requests are pending from long time, better skip that project as likelihood of being accepted is dismal. It is recommended to focus on hot cakes.
- My changes before commit are properly commented
- Am I making right commentary about the change and politely requesting for a review?
- Is my commit message going into PR rightly describe about the change I made?
I was working on a change on my forked repository but before I can submit my change, main repository merged some changes from elsewhere and now I am not in sync or branch head is running some commits behind the main repository.
It is a common issue generally occur when developers choose to follow develop and release side by side model.
# show branches
$ git branch -v
# show remote sources
$ git remote -v
# add a new source stream
$ git remote add <name ex. upstream> <repository link ex. main repository link>
# check again
$git remote -v
# pull code from main repository
$ git pull <source name ex. upstream> <branch name generally same as current working branch>
# if changes are already commited, check logs
$ git log
# Here our commit must be on top.
# push changes
# git push <source name> <branch name>
ex.
$ git push origin master
# Now you can raise PR from web ui
No problem, pypy versions are not available for LoP yet. Skip pypy version(s) or write it under exclude: of matrix/job.
Further details : For sindresorhus/array-union#8 and other related one we found there are 1k repositories here https://github.com/sindresorhus?tab=repositories , so I would suggest that we refrain from raising any further PRs on this entire set, at least for now because with the kind of blunt response he has given, there is a chance that he may end up reporting one of these as spam or something. I know this is pure speculation, but lets play a bit safe for now (cc @gerrith3)
If you found any similar lists which are to be refrained feel free to update here.