![]() ![]() Self promotion of music, playlists, services, products. If you have questions about this rule, or message the moderators. None of these things are good, so consider messaging the mods before actually posting about projects like those discussed above.īe specific, concise, and polite when requesting music. Publicizing the work being done behind the scene can often jeopardize the project or put those doing the work in legal danger if they are not very careful. Some things are often best kept under wraps, such as siterips of major music sites. Talk to moderators before posting about projects. Content in this style must either have a longer text post/comment attached to it discussing the collection in some depth or be substantial in some other way. Content that solely positions itself to show off large amounts of content do not contribute to the conversation revolving around collecting music and auxiliary parts of music. Content revolving around this topic will be removed.Īvoid posting simply to brag about the size of your music collection. This is not the place for requesting invitations to music trackers. It will not be tolerated.ĭo not request or offer invites to trackers or other private music sharing sites. Do not harass other members of this community for their music or access to their files, or request access to files in a way that comes across as entitled. Users frequently choose to generously share music through various outlets. Read the Rulesĭo not beg for access to music or make demands regarding requests. Make sure to check out the wiki for more info. Whatever your persuasion, if you hold an interest in anything relating to the above-then you'll fit right in! Others just wish to learn about music formatting, organizing and pirating. Some collect purely for rare and obscure music, to preserve pieces which might otherwise be lost in time. Some hoard music because they believe that the internet will not remain free and open in the foreseeable future. We are a group of people engaged in collecting as much digital music as possible. All other labels are treated as patches that do not change the API.Home of the compulsive music collectors who are looking to expand, archive or organize their music library. The issue-labels input allows to define issues labels that should be considered as minor versions (API extensions). This is useful when generating or applying tags. The tag input allows to use a custom tag for tagging. This output is unavailable, when the tag input is used. The previous latest tag before this action ran. Optional A comma-separated list of issue labels that changes the bump level from patch to minor (Default: enhancement). Will not perform any version bumping, but adds the provided tag. ![]() Optional Custom tag to be added to the current SHA. ![]() Optional A comma-separated list of branch names or regular expressions. This is useful when tagging of merge requests. This input is useful if subsequent steps manipulate a different branch, which should get tagged. This is useful if the triggering action's branch is different to the final action. Optional Sets a branch to perform the action on. Optional If not FALSE (case insensitive), then the action adds a v to prefix the tag. Valid values are major, minor or patch (Default: patch) with-v It is very handy if a build or cleanup steps will extend the initial commit or merge request. This input is useful if the release version has to be known for other steps before actually tagging the final commit. Optional If the value is not FALSE (case insensitive), the action performs all steps, but omit the actual tagging. Required The github token for accessing the repository. This action has been inspired by anothrNick/github-tag-action, but is written completely in javascript and runs directly within the runner.Īutotag-action uses Octokit for tagging and does not depend on checking out the repository. autotag-action also supports prereleases for non-release branches and custom tags. If a commit message fixes an issue (using fixes #issuenbr style messages), then autotag-action will check wether the corresponding issue was labled as enhancement that triggers a minor release, or a bug fix that will be treated as a patch. Use #major, #minor, or #patch tags in your commit messages and autotagger will increase your version tags accordingly. This action scans your commit messages for fixed issues and semver changes. It helps you to stay on top of your release management and release your code quickly and often through GitHub's tag-based release functions just by pushing to your repository. A lightning fast autotagger for semver-tagging. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |