skpkg: migrate documentation, README, and public static files

[zmx27]

No description provided.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 97.23%. Comparing base (fc5bac1) to head (c83de82).
Report is 1 commits behind head on migration.

Additional details and impacted files

@@            Coverage Diff             @@
##           migration     #203   +/-   ##
==========================================
  Coverage      97.23%   97.23%           
==========================================
  Files             20       20           
  Lines            903      903           
==========================================
  Hits             878      878           
  Misses            25       25           

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[sbillinge]

I know htis is a draft but I left some comments. I expect that many of the "deleted" files will reappear as you move them over. Thanks for putting the PR up early as a draft!

[sbillinge]

This should stay as it was.

[sbillinge]

we need all these old changelogs.

[sbillinge]

this should be my columbia email if possible. If this change is coming from skpkg, could we put in an issue to change it there?

[zmx27]

This change comes from the original pyproject.toml file, which listed your non-Columbia email. I can change this back

[sbillinge]

gotcha. Yes, I would like this changed to my Columbia email in this case, though it was a good choice to have the instinct to change it the way you did....

[zmx27]

@sbillinge when trying to migrate the doc/manual directory, I found that certain files were too large (exceeds 500KB) and pre-commit wouldn't pass. How should I go about doing it?

[sbillinge]

@zmx27 I often see merge commits in your commit history. These should appear very rarely or never. Why are they happening?

[zmx27]

@sbillinge Sometimes it's because I forget to run git pull upstream after a previously open PR is merged, but in a lot of the other times I feel that it's due to the CI making changes to the code on GitHub, and my local repository cannot keep up. My pre-commit hooks are on, and everything should have already passed pre-commit when I make a commit, so I don't know what's going on. On a side note, how should I migrate the doc/manual folder, if at all? Some of the files seem to be too large, thus failing pre-commit. I think that this is my last step before making final checks.

[sbillinge]

@sbillinge Sometimes it's because I forget to run git pull upstream after a previously open PR is merged, but in a lot of the other times I feel that it's due to the CI making changes to the code on GitHub, and my local repository cannot keep up. My pre-commit hooks are on, and everything should have already passed pre-commit when I make a commit, so I don't know what's going on. On a side note, how should I migrate the doc/manual folder, if at all? Some of the files seem to be too large, thus failing pre-commit. I think that this is my last step before making final checks.

so this not the correct workflow. First always sync upstream and build your new branch from the base. But if you did that, you don't synchronize your local with upstream except on rare occasions. which would be discussed in the PR convo. If things have diverged with upstream and there is a conflict, we would like to understand why before just simply merging.

For the manual migration, we do want to move it over. Make a PR moving everything that is not too bg and we will merge that. Then describe in the PR which files are failing "too large" check and we can discuss.

[zmx27]

I think I will just redo this branch instead. I will make a new PR when I'm finished.