You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
galaxy001
changed the title
Store post-to-issueID list to git repo and allow overwrite listed issues accroding to list
Store post-to-issueID list to git repo and allow overwrite listed issues accroding to this list
Oct 26, 2017
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:
And if the repo owner think issue 3 is misformatted, he can modify the list to:
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 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:The text was updated successfully, but these errors were encountered: