Migrating Pull Requests from ethereum/EIPs to ethereum/ERCs

[lightclient]

If you are trying to move a PR you made to ethereum/eips over to ethereum/ercs, the steps below will guide you through the process:

1. Fork this repository within GitHub:

   1. Navigate to ethereum/ERCs.
   2. Find the "Fork" button in the upper right side of the screen and click it.
   3. Proceed with repository creation.

2. Clone your fork locally:

   1. git clone https://github.com/{user}/ercs

3. Enter the newly created ercs folder:

   1. cd ercs

4. Add your fork of the EIPs repository as a remote:

   1. git remote add eips https://github.com/{user}/eips

5. Fetch that remote to download your branches:

   1. git fetch eips

6. Now checkout the branch related to your original PR:

   1. git checkout {branch}

7. Rebase your branch against the ERCs repo:

   1. git rebase master
   2. Please note, you do not need to update any references of EIP to ERC; particularly in the relative links. Even though [ERC-X](./eip-x.md) doesn't correctly render in this repository, we're currently building the full eips.ethereum.org still in the ethereum/eips repository. So until we resolve this in Pending tasks for ERC migration #1, we will continue using this relative linking format.

8. Push your branch to your ERCs fork:

   1. git push -u origin {branch}

9. Now you can recreate your pull request:

   1. Navigate to https://github.com/ethereum/ERCs/compare
   2. Select your newly created fork and branch
   3. open a new PR to this repo.

Additional notes:

• Do NOT link to ERCs using their filename. Link to ERCs using [ERC-XXXX](./eip-XXXX.md).

[TtheBC01]

I think in step 4 of your instructions you need to flip remote and add around

[lightclient]

@TtheBC01 you're right, thank you.

[TtheBC01]

is it ok to just fork the new ERCs repo, add our ERC under the number that was assigned from the EIP repo and create a new PR? or is it preferred to stick to this rebasing procedure?

[lightclient]

You can also do that if you prefer.

[cfries]

I mentioned this before, but what worked for me was to do everything up to step 7, then, not rebasing, creating a new branch for the PR from ERC master, then chery-picking manually all changes from the EIP pull request branch.

Step 7 did not work because I got conflicts due to the renaming of the folders.

[Xeway]

For 8.i., the command that worked for me is git push origin HEAD:{branch}

[github-actions]

There has been no activity on this issue for 1 week. It will be closed after 3 months of inactivity.

[github-actions]

There has been no activity on this issue for 1 week. It will be closed after 3 months of inactivity.

[github-actions]

This issue was closed due to inactivity. If you are still pursuing it, feel free to reopen it and respond to any feedback.

[github-actions]

There has been no activity on this issue for 1 week. It will be closed after 3 months of inactivity.

[18211308]

Член

...

[github-actions]

There has been no activity on this issue for 1 week. It will be closed after 3 months of inactivity.