git format-patch -k --stdout
where -k is number of commits you want to create patch for from the latest situation. --stdout allows to see the merged diff of all these commits, hence preferred to check before creating patches.
Now when you are sure, create patch files using
git format-patch -k
if k is 3, it will create 3 patch files for 3 past commits.
| {"name":"Solidity","settings":"{\"settings\":\"{\\r\\n \\\"workbench.startupEditor\\\": \\\"welcomePage\\\",\\r\\n \\\"workbench.colorTheme\\\": \\\"Solarized Light\\\",\\r\\n \\\"workbench.editorAssociations\\\": [\\r\\n {\\r\\n \\\"viewType\\\": \\\"jupyter.notebook.ipynb\\\",\\r\\n \\\"filenamePattern\\\": \\\"*.ipynb\\\"\\r\\n }\\r\\n ],\\r\\n\\t\\\"editor.inlineSuggest.enabled\\\": true,\\r\\n \\\"files.autoSave\\\": \\\"onFocusChange\\\",\\r\\n \\\"editor.wordWrap\\\": \\\"on\\\",\\r\\n \\\"solidity.telemetry\\\": false\\r\\n}\"}","extensions":"[{\"identifier\":{\"id\":\"github.copilot\",\"uuid\":\"23c4aeee-f844-43cd-b53e-1113e483f1a6\"},\"displayName\":\"GitHub Copilot\"},{\"identifier\":{\"id\":\"jebbs.plantuml\",\"uuid\":\"d95cb424-7a5a-4e08-9698-107d6fd590cf\"},\"displayName\":\"PlantUML\"},{\"identifier\":{\"id\":\"juanblanco.solidity\",\"uuid\":\"25baab03-fe9a-40c7-b683-55c9a0a92480\"}},{\"identifier\":{\"id\":\"nomicfoundation.hardhat-solid |
| For first time setup:- | |
| gcloud auth login - To login into your google account | |
| gcloud config set project PROJECT_ID | |
| gcloud cloud-shell ssh --authorize-session |
$ systemd-analyze
Startup finished in 4.026s (kernel) + 47.655s (userspace) = 51.681s
graphical.target reached after 47.654s in userspace.
47 seconds might sound painful but that was around 2 minutes and 5-15 seconds in ubuntu and 10 minutes in Windows :)
git rebase -i HEAD~2 #assumed last two commits need to be squashed
Similarly HEAD~3 for squashing last three and so on
As a result vi or your any other text editor opens up top two lines(because we are squashing two commits) will be
pick [commit-sha] [commit-message]
pick [commit-sha] [commit-message]
There will be more lines below them but all would be commented
| //SPDX-License-Identifier: MIT | |
| pragma solidity 0.8.7; | |
| contract HelloWorld { | |
| // Declaring a global variable that stores the number | |
| uint myNumber; | |
| /** @dev Store a given number into a variable |
| // SPDX-License-Identifier: GPL-3.0 | |
| pragma solidity >=0.7.0 <0.9.0; | |
| /** | |
| * @title Ballot | |
| * @dev Implements voting process along with vote delegation | |
| */ | |
| contract Ballot { | |
One simple thing will be to before creating changes to file for next commit in separate pull request, checkout new branch tracking upstream repository branch against which you want to create your pull request.
But let say you have alreay committed the changes into the branch which might have already unaprroved pull requests.
In thaaat case you have to do it little bit new way actually you have to cherry-pick the commit and put on a new branch. Then pull request against that other repository will be automatically creating new pull request against same original branch of that repository.
So how do we do that?
first you will need commit hash of that commit which you want to put on top of new branch.
To get commit hash of that particular commmit do git log in the branch where you commited the required changes.
There you will see the hash, commit message, timings and other info which will help you identify the required commit.
After copying that hash(long ascii string - sha1) you can quit using q
Yes!
You need a browser extension
@everyone
https://addons.mozilla.org/en-US/firefox/ (AMO)
Search '@everyone' there in the search bar or directly go to this link https://addons.mozilla.org/en-US/firefox/addon/tageveryone/