Arbitrarymarkdown

[poisonous-milk]

Let us see if #904 still happens

Fixes #938
Supersedes #939

[shiftkey]

This seems unrelated to the other changes - could you add it back in?

[shiftkey]

There seems to be some changes in here related to the issue search. Could you refresh my memory on which issue those changes are addressing?

[poisonous-milk]

@shiftkey
Those are about #839
My bad. I should create a new branch of master when I started implementing this API. I will soon submit a new version without dependency on my earlier commits.

[shiftkey]

@chenjiaming93

Given there's some other branches for Pull Request Assignee and Pull Request Merged, you could have a go at rewriting this branch to contain just those commits.

I'll walk you through the process to explain what's happening. You should have a remote named origin and one names upstream, you can check them like this:

git remote -vv

If you only see origin listed, run this:

git remote add upstream https://github.com/octokit/octokit.net.git

And now you've done that, ensure you've got the latest changes from both repositories:

git fetch --all

We'll switch to our branch we're working on:

git checkout arbitrarymarkdown

And we're going to put it back to whatever is the latest from upstream:

git reset upstream/master --hard

If at this point you feel unsure about continuing, this is how you get back to your previous state:

git reset origin/arbitrarymarkdown --hard

Now, we're going to add those three commits onto our new branch:

git cherry-pick cde7254
git cherry-pick 7c1c86f
git cherry-pick b084d9f

Once you've tested out things with a .\build BuildApp, you can push this to reset the PR:

git push origin arbitrarymarkdown --force

[poisonous-milk]

@shiftkey no problem. I will do that. Thx

[shiftkey]

Closing in favour of #957