Comments (5)
Left my other questions/comments on PR 😊
from changelog-reader-action.
@aroemen Hi! Thanks for creating this issue!
I really like the idea of adding more properties the tool can deduct from the CHANGELOG.md
file. It would be useful for a lot of workflows.
Can you give me more information about the properties you want to add? Here are my first thoughts/questions after only reading their names:
tag_name
: is it the version number? or something else?release_name
: this seems to be a name/title build from the version number. How can we do that without being opinionated? (Given that since the user already know the version number he can build this name by it self)prerelease
: I love this one. I need to look at how to get this informationbody
: is this a new property or a renaming of thelog_entry
property?
from changelog-reader-action.
Also if you think of more property ideas, please let me know 😉
from changelog-reader-action.
@mindsers I created a fork and put in a pull request for your repo here. The readme has more information on the additional property outputs. Let me know if you'd like more detail. Thanks!
from changelog-reader-action.
Closed by #17
from changelog-reader-action.
Related Issues (20)
- Getting ##[error](intermediate value)(intermediate value)(intermediate value) is not iterable HOT 9
- Suggestion: Action should throw an error if specified target version is not found. HOT 3
- Add validation of the changelog HOT 10
- Add warning and error messages for the validation feature
- Use a configuration file
- Preleases in Python do not parse appropriately HOT 2
- Replace newline with spaces HOT 4
- Warning about 'validation_depth' HOT 2
- Link references are filtered out from version entry HOT 9
- [Question] Finding a CHANGELOG.md dynamically? HOT 1
- Error: releasedVersions is not defined HOT 4
- latest version does not capture changelog content HOT 5
- Version's sections are restricted HOT 10
- exporting changelog entry to tmp file HOT 3
- Upgrade node version used by the action from 12 to 16 HOT 1
- `set-output` command deprecation HOT 5
- `set-output` command deprecation HOT 1
- The README claims `validation_depth` is set to `0` by default, but it isn't. HOT 3
- Update node version to node16 or higher HOT 4
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from changelog-reader-action.