Guillaume Giudicelli
Guillaume Giudicelli
Needs a reviewer, then there may be additional comments to address. @idaholab/moose-ccb
I ll do the squash
For fixing this, one obvious solution would be to rewrite MOOSE history and change these commits. They could point either to a dedicated sockeye issues issue, or ported sockeye issues...
What I like about the "2 issue in one issue" solution is that if it's not enough, we can go back and do the other solution easily. Once we have...
> We would need to create a Sockeye issue 19845, right, which we probably can't do? you could either create 18,000 dummy issues to get to 19,000 or maybe just...
`git commit --amend` to modify the last commit message. Then add : "refs #23207" to the message
@loganharbour has rights to do that @socratesgorilla can you as well?
@AyaHegazy22 what's the status on this? Should we take it over?
@aprilnovak what is the status here? Should we take this over or did it get added elsewhere?
If a new or existing material property can be released and is of interest to the community then it should be. There's no use handicapping our open-source capabilities when we...