Force pushing to master

mixmix commented 2 months ago

Is this a regression?

Yes

Description

Went to pull the master branch and nope

Please provide the exception or error you saw

➜ git pull origin master 
remote: Enumerating objects: 1100, done.
remote: Counting objects: 100% (1100/1100), done.
remote: Compressing objects: 100% (533/533), done.
remote: Total 1100 (delta 536), reused 1075 (delta 527), pack-reused 0
Receiving objects: 100% (1100/1100), 756.06 KiB | 916.00 KiB/s, done.
Resolving deltas: 100% (536/536), completed with 229 local objects.
From github.com:input-output-hk/atala-prism-wallet-sdk-ts
 * branch            master     -> FETCH_HEAD
 + a851b69...76f4f48 master     -> origin/master  (forced update)
fatal: refusing to merge unrelated histories

Please provide the environment you discovered this bug in

git

Proposal

Don't force push to master ? Makes it annoying for contributors to play along

mixmix commented 2 months ago

Context: I'm pull the repo to start into contributing features.... and ... it looks like 5.0.0 has been straight up orphaned?

:crying_cat_face:

So yeah ... where do I start when it comes to contributing?

elribonazo commented 2 months ago

Hey buddy,

As part of the hyperledger migration our commits had to be re-signed and we had to force-push the history, and relink tags to their correct place, all should be good now

elribonazo commented 2 months ago

https://github.com/input-output-hk/atala-prism-wallet-sdk-ts/tree/v5.0.0

elribonazo commented 2 months ago

https://github.com/input-output-hk/atala-prism-wallet-sdk-ts/releases/tag/v5.0.0

elribonazo commented 2 months ago

I will try to solve this by re-creating the last releases, etc.

During a while today the release will be set to draft and also the tags will be re-configured and releaases enabled back again later.

mixmix commented 2 months ago

I'm really sorry ... I'd love to talk to the bureaucrat which forced you down this path :cry:

also, more fun treats