After Upgrading my TYPO3 website from 8.2 to 8.7 version, the image manipulation has been removed from the news item images, how can I enable it or install it back ?
Due to new TCA requirements in TYPO3 8.7, this feature is not enabledin the current version of ext:news
I created this pull request with modified TCA which brings back the image cropping tool.
If you don't want to wait for the patch to be merged, you can easily apply it manually to your ext:news TCA. Feel free to update the pull request, if something is missing.
Related
Is there a way to automatically update the "Releases" version number on a Github page? Either from automatic machinery within Github, or using some API to update it?
(See the release number "3.5.0" in the image below...) Thanks.
This sidebar component shows you the latest release (I believe). If you want to add a release, that can be done using the REST API. You can also update the release using the REST API.
Note that it isn't sufficient to just push a tag here. A release on GitHub is associated with a tag, but it can also have a message and assets (usually binaries or source code) associated with it. You do need such a tag, but you also need to create the actual release on GitHub.
If you want an example of how this can be done with shell scripting, Git LFS has a script that performs this task as part of the release process.
I've joined a project which uses Github actions & releases. Unfortunately, naming convention of release tags changed in the past (probably due to migration from Travis CI).
Until a certain point of time, the tags were like this (not sure why the numbers were so high):
v1018.0.0
v1018.1.0
v1020.0.0
v1024.0.0
Then someone switched to semantic versioning (which is great btw):
v2.5.1
v3.0.0
v3.1.0
v3.1.1
Our CI/CD works just fine, but we have some issues:
We use Release Drafter. It creates a description for a new release which should consist of all PRs since the previous release. But now it compares current state of our master branch not with the latest tag (v3.1.1), but with a tag with the highest major number (v1024.0.0). Which means the draft always consists of 100+ PRs merged since one year ago. So we end up deleting the whole release description, because noone has time to analyse that.
It's messy. Github always suggests v1024 as the newest version: when creating new releases, when switching between tags and so on.
My two questions are:
Is there any safe way to update names of all old tags? F.e. change v1024.0.0 into v0.1024.0. Doesn't have to be automatic. Keep in mind it should update the tagnames only, I don't want to change release date, assets etc. I think that editing a release using Github UI would in fact create a new tag based on master (and maybe even release it to live server?)
If not, is there any way to tell Release Drafter that it should use the latest tag instead of the highest one?
Well a little googling would tell you many things :)
How do you rename a Git tag?
https://gist.github.com/rponte/fdc0724dd984088606b0
Yes you can update tags (see first link)
Yes you can get the latest tag - see second link.
I document my software using the README.org file, which is rendered nicely in the master branch in GitHub. Now, suppose I create a tag v1.0 and want to share a link to that tagged version with others. Unfortunately, when one follows that link, he does not find my README.org nicely rendered, but only the archived code. So, what is the correct way of documenting a tagged version at GitHub? (of course, I am looking to re-use my README.org).
I've found out that in github you can use a Latest Release button or link to always clone the latest tag from that project without specifically specifying the version number, however if I use something like this: (links are just examples project is private)
https://github.com/company/project1/releases/latest (this is how I've learned the latest release link should be accessed)
it just redirects me back to:
https://github.com/company/project1/releases/
My guess is that I have to enable the Latest Release button/tag somehow? How will I do it?
It works only if your release has an artificat associated to it.
See for instance: https://github.com/reactiveui/ReactiveUI/releases/latest
If you define releases without ever attaching a binary to any of them, then 'latest' redirects you to the releases page of your project indeed.
We have a group-developed metadata conventions document for a particular group of ocean models stored as github-flavored markdown at https://github.com/ugrid-conventions/ugrid-conventions
and now we would like to "release" the current version of this markdown document at version 1.0 (and continue the development of the conventions for future releases).
I understand that github has releases, but we don't want a zip file containing the markdown document, we just want a "version 1.0" markdown document. We could also like to preserve the changes so that people can see what changed relative to previous versions as we go forward.
Should we just copy the existing document ugrid-conventions.md to ugrid-conventions_v1.0.0.md, or is there a better way?
I'd suggest creating a tag for each release. Tags automatically get listed on GitHub's Releases page (in fact, every Release is associated with a tag), and you can also link directly to files within a tagged commit. For example, if you created a tag named v1.0, you could send folks to https://github.com/ugrid-conventions/ugrid-conventions/blob/v1.0/ugrid-conventions.md to see the 1.0 version of that file.