Venus Source Control Best Practices

Long time software developer but fairly new to Venus. Trying to get some of these files under source control, trying to break down which files can be under source control and which files are temporary/transient. Does this look reasonable?

Can be under source control:
*.hsl
*.med
*.sub
*.stp
*.lay
*.res

Should not be under source control:
?

2 Likes

One the Hamilton folks would be able to say more definitively, but for Hamilton methods, my .gitignore files generally include the following line that excludes temporary files created when method editor is open:

~*

I think the files you’ve got listed need to be committed all together or you run the risk of creating some weird errors when trying to run the Venus methods

3 Likes

All files need to be committed together, otherwise it’s impossible to run your assay.

I never have any issues with checksums. However we have it here quite strict. If one needs to modify any controller during development. They inform me about it, we never work together on the same file at once.

Everything in our method folder is under version control via git. Except like above the ~ files.

1 Like

that is not true.

Methods:
.hsl
.med
.stp
.sub

Layout:
.lay
.res

the methods and layout can be independent of each other, but you do need all files to run.

1 Like

Assuming you would have a deck + method connected to eachother…you need to commit them together. Otherwise you are correct. However, you would not be able to run your assay if you don’t have a decklayout on method.

I think @chips-a-hoai is saying that they do not need to be committed together, they could be in different repos, or not committed at all and ignored, as long as on disk all files are present. The layout file can be in a separate location to the method file.

1 Like

Oh I see, yes :slight_smile: Then he is right.