I use a GPG key to sign my git commits.
An error like this one might be a sign of an expired GPG key.
error: gpg failed to sign the data fatal: failed to write commit object
People
:bowtie: |
😄 :smile: |
😆 :laughing: |
😊 :blush: |
😃 :smiley: |
:relaxed: |
😏 :smirk: |
😍 :heart_eyes: |
😘 :kissing_heart: |
😚 :kissing_closed_eyes: |
😳 :flushed: |
😌 :relieved: |
😆 :satisfied: |
😁 :grin: |
😉 :wink: |
😜 :stuck_out_tongue_winking_eye: |
😝 :stuck_out_tongue_closed_eyes: |
😀 :grinning: |
REST APIs | GraphQL | |
---|---|---|
one URL serves only one request which leads to 100s of URL to maintan | One URL to serves every request | |
Multiple roundtrip to get various kinds of data | Single trip to get various combinations of data | |
Unwanted data travel from server to client (Wastage of bandwidth) | Only required data is travelled which make response light and minimum number | |
No flexibility | Much more flexible | |
Keeps Backend and frontend team tightly coupled | Backend and frontend team are loosely coupled | |
Change in structure of APIs needs the client to change as well | Change in structure of API is not needed in client side | |