Update name and URL of "EByte RF E70 library" #4036
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
per1234
added
topic: URL change
MatteoPologruto
approved these changes
Feb 15, 2024
Contributor
MatteoPologruto
left a comment
MatteoPologruto
left a comment
There was a problem hiding this comment.
Done:
2024/02/15 13:51:22 Loaded 6647 libraries from DB
Removing EByte LoRa E70 library
Success!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR consists of two changes:
https://github.com/xreef/EByte_LoRa_E70_Series_Library.gittohttps://github.com/xreef/EByte_RF_E70_Series_Library.git(companion to Update URL of "EByte RF E70 library" inrepositories.txt#4035)EByte LoRa E70 librarytoEByte RF E70 library(resolves Library name change request EByte_LoRa_E70_Series_Library to EByte_RF_E70_Series_Library #4033)Since the name change operation on the database is actually a removal followed by automated re-indexing on the next job run, the URL update will occur as a matter of course. For this reason, the only operation required from the backend maintainer is a standard name change procedure.