Store post-to-issueID list to git repo and allow overwrite listed issues accroding to this list

[galaxy001]

Repo owners may have many misformatted issues inserted to their blog repo, and Github only allows us to modify an issue. So, it is better for the local tool to output a post-to-issueID planning list first. And then allow a user to modify the list to use misformatted issues for new posts.

For example, there are 1 post and 5 issue on Github. The repo owner writes 2 new posts locally and is ready to push it.

The local tool could make a list like this:

2017-11-22-Hello-World.md   5
2017-11-23-Welcome.md       6
2017-11-23-Just-Wrote.md    7

And if the repo owner think issue 3 is misformatted, he can modify the list to:

2017-11-22-Hello-World.md   5
2017-11-23-Welcome.md       3
2017-11-23-Just-Wrote.md    6

Then, he use the local tool to update github issues in overwrite mode, so the tool overwrite issue 3 and issue 5, and insert issue 6.

• I am not sure whether it is practical to check there is no change in issue 5 first and then skip overwriting issue 5.
• There should also be a normal mode to only insert issue 6 since overwriting existed issues may take too much time.

---

I think the list can also used for webpage js script to get the right issue number without searching. If we put the list in assets path.

We may add permalink to the list for a easier searching. Like this:

5   2017-11-22-Hello-World.md   2017/11/22/Hello-World
3   2017-11-23-Welcome.md       2017/11/23/Welcome
6   2017-11-23-Just-Wrote.md    2017/11/23/Just-Wrote