New setup working release with aliases

[RossanaTat]

Updated:

• setup_working_release to work with stamp alias
• Tests for working release
• How logs are saved and loaded to use stamp alias
• Tests for log save and load
• Tests for functions interacting with Github

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

• 🔍 Trigger a full review

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch use_stamp_rt

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[dana89co]

Hi @RossanaTat, I reviewed it and some of the tests are not passing regarding this file, so maybe we need to check that. However, I tested in pipload and I have made the changes accordingly. I will send you PR in a bit

[RossanaTat]

Hi @RossanaTat, I reviewed it and some of the tests are not passing regarding this file, so maybe we need to check that. However, I tested in pipload and I have made the changes accordingly. I will send you PR in a bit

Sure thanks, fixing the tests now!

[dana89co]

Hi @RossanaTat, I do not think this function exists. We can use stamp::st_alias_get or stamp::st_alias_list. Maybe we should use the last one here?

[dana89co]

@RossanaTat , wait is this actually happening? It should no re-register. If the folder is already created st_init does not do anything. Is that not the case?

[RossanaTat]

Hey @dana89co, this is happening when you try to initialize the same alias for different folders, which {stamp} by default does not accept. This is because some root folders paths, like the one for aux data, are release specific. For example, if I call setup_working_release("20251211", "TEST") and then setup_working_release("20251205", "TEST") in the same session, {stamp} will error saying that the "aux" alias was already registered for ".../.../aux_data/20251211_TEST" and therefore cannot point now to ".../.../aux_data/20251205_TEST". This is correct behavior in {stamp} and ideally a situation that does not occur often, as we work with one release per session.

However, in order to make it more flexible, I've updated the function in the following way (refer to latest commits):

• setup_working_release has an additional argument alias_include_release which is by default FALSE. When the user sets it to TRUE, when stamp initializes the aliases, the alias name will contain the release date for those folders which are release specific, so that no conflict arise.

Feel free to give it a try and let me know if you have questions :)