Move this repository to kiedtl/ #81
Comments
|
As long as all the issues, history, redirects from the old URL (for git remote/upstream stuff) get transferred properly I think we would be fine. Github should automatically handle all of that as far as I'm aware. However I have one doubt, the (long proposed) yet to be published package in the PowerShell Gallery was supposed to be named lptstr-winfetch. Will we be changing this, as a result of the transfer? |
|
Uhg, that's a rough side. |
|
Sounds like it should be fine, we should also let the chocolatey thread know (#38), as @jakublevy is maintaining a package for that. There are also some references to the URL in the |
|
I will push URL changes to chocolatey with the next version. |
|
We can probably release 3.0 after the shift (couple of new stuff - weather info, native image printing etc.) |
|
Agreed, I've had a look over at the codebase and everything looks good, we'll wait for the move and then create a new release, which should really be v2.1.0, as it's not a major overhaul. Also when we update the scoop manifest this would also be a good time to address #77. |
|
We'll use |
|
The v2.1.0 release can be done now, after which the Choco and wiki updates can be done. |
|
@rashil2000 Can we do the release now? The Scoop maintainers seem to be busy; I don't think we should wait for the PR merge any longer. |
|
Sure, I've already done the release notes, pretty sure I mentioned everything, was just waiting for them to merge the PR first, but you're right there's no point in waiting any longer. You may want to update the PR to point to the new release once we create it. |
|
Looks good, all green from me! |
|
Done v2.1.0 released 🎉 |
|
Chocolatey package updated. |
|
@jcwillox The script metadata is out of date (still shows v2.0.0) Is there a way to correct it in the 2.1.0 tag branch itself? The updated metadata is necessary for publishing pwshfetch-test-1 to PSGallery. @jakublevy I think you'll need to update the file checksum once this change is made. |
|
Oh, I didn't inspect the actual file, @rashil2000, you're right, thanks. |
|
Haha we totally missed that, I'm not aware of any way to update the tag, especially without breaking things, we're probably best just creating |
|
https://stackoverflow.com/a/21466838 It is generally not a good idea to update tags, but I don't think we have any infra in place that would break if we just do it. Correct me if I'm wrong. |
|
The scoop manifest won't update and it'll have the wrong hash, honestly just safer to create a patch release (which is basically what that stackoverflow answer says) |
|
This issue can be closed - the only item left was the PSGallery package. It is being tracked in #13 |
I created the
lptstrrepository a few years ago to store my "serious" projects. The idea was to have a place where I could keep side projects I intended for broader use, and keep other things (dotfiles, random scripts, experiments) in my user profile.However, it's become a bit tedious to follow this pattern and this rule hasn't held true for a while. There are plenty of half-assed junk projects in
lptstrand a few "serious" projects inkiedtl, so I've decided to move everything fromlptstrtokiedtland just get rid of that pseudo-organization.Of course, this will be easy to do for things like chmap, but not so easy for Winfetch, as the repository names are baked into a lot of places. I'm making a list of these places; once I believe I've gotten everything down, I'll transfer the repository and change all the URL references.
List of things to be changed/done before move:
winfetch.ps1metadataAfter:
@jcwillox @rashil2000 Let me know if the repository transfer will affect anything else. Of course, all maintainers will continue to have access after the transfer.
The text was updated successfully, but these errors were encountered: